Difference between revisions of "Roadmap"

From Drafts
Jump to: navigation, search
Line 4: Line 4:
  
 
First, make the most of what exists already and archive things. Even if some changes have to be made in later development they are always easier if the documents have been following some kind of order/classification.
 
First, make the most of what exists already and archive things. Even if some changes have to be made in later development they are always easier if the documents have been following some kind of order/classification.
*Publish the [http://www.constantvzw.com/cn_core/guests/guests] --> work in php; needs redesign first
+
*Publish the [http://www.constantvzw.com/cn_core/guests/ guests] --> work in php; needs redesign first
*reskin the [http://www.constantvzw.com linxx] pages --> mock-up
+
*reskin the [http://www.constantvzw.com/linxx linxx] pages --> mock-up
 +
*reskin the [http://www.constantvzw.com/cn_search/search.php3  search] pages --> mock-up
 
*Archive vj9 using the existing cn_core (design templates, adjust cn_core)
 
*Archive vj9 using the existing cn_core (design templates, adjust cn_core)
 
*Add Constant-index button to each page
 
*Add Constant-index button to each page

Revision as of 18:10, 15 December 2005

Let's try to give a reasonable timeline for the development of the website.

Two speeds.

First, make the most of what exists already and archive things. Even if some changes have to be made in later development they are always easier if the documents have been following some kind of order/classification.

  • Publish the guests --> work in php; needs redesign first
  • reskin the linxx pages --> mock-up
  • reskin the search pages --> mock-up
  • Archive vj9 using the existing cn_core (design templates, adjust cn_core)
  • Add Constant-index button to each page
  • Fix flow bug on index page
  • Skin newsletter subscription

Second, long term development. The big picture. How to organise and build the infrastructure of the website and integrate ideas/input from the whole team.