Difference between revisions of "Roadmap"

From Drafts
Jump to: navigation, search
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:Website development]]
 +
 
Let's try to give a reasonable timeline for the development of the website.
 
Let's try to give a reasonable timeline for the development of the website.
  
Line 5: Line 7:
 
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(FS 1)
*reskin the [http://www.constantvzw.com/linxx linxx] pages --> mock-up
+
*reskin the [http://www.constantvzw.com/linxx linxx] pages --> mock-up + PHP(FS 1 + NM 1)
*reskin the [http://www.constantvzw.com/cn_search/search.php3  search] pages --> mock-up
+
*reskin the [http://www.constantvzw.com/cn_search/search.php3  search] pages --> mock-up(FS 1 + NM 1)
*reskin the [http://www.constantvzw.com/fonts.php fonts] pages --> mock-up
+
*reskin the [http://www.constantvzw.com/fonts.php fonts] pages --> html(FS 0.5)
*Add Constant-index button to each page
+
*reskin the [http://www.constantvzw.com/news news] pages --> work in movable type...(FS 1)
 +
*Add Constant-index button to each page(NM 1.5)
 
*Fix flow bug on index page
 
*Fix flow bug on index page
*Skin newsletter subscription
+
*Skin newsletter subscription --> html(FS 0.5)
 +
 
 +
details(NM 0.5 + FS 0.5)
 +
 
 +
end of January 2006
 +
 
 +
----
  
 
*Archive vj9 using the existing cn_core (design templates, adjust cn_core)
 
*Archive vj9 using the existing cn_core (design templates, adjust cn_core)
 +
 +
*Design mockups (FS 2)
 +
*Design backend (FS 1.5)
 +
*Design templates (FS 3)
 +
*Design polishing (FS 1)
 +
 +
*Adapt existing backend to new edition (NM 1)
 +
*Connect backend to image galleries (NM 1)
 +
*Backend text (NM 1.5)
 +
*Backend sound (NM 1.5) <--> Radioswap?
 +
*Produce templates (NM 2)
 +
 +
*TTS?
 +
 +
mid-March 2006
 +
 +
----
  
 
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.
 
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.

Latest revision as of 11:13, 13 January 2006


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(FS 1)
  • reskin the linxx pages --> mock-up + PHP(FS 1 + NM 1)
  • reskin the search pages --> mock-up(FS 1 + NM 1)
  • reskin the fonts pages --> html(FS 0.5)
  • reskin the news pages --> work in movable type...(FS 1)
  • Add Constant-index button to each page(NM 1.5)
  • Fix flow bug on index page
  • Skin newsletter subscription --> html(FS 0.5)

details(NM 0.5 + FS 0.5)

end of January 2006


  • Archive vj9 using the existing cn_core (design templates, adjust cn_core)
  • Design mockups (FS 2)
  • Design backend (FS 1.5)
  • Design templates (FS 3)
  • Design polishing (FS 1)
  • Adapt existing backend to new edition (NM 1)
  • Connect backend to image galleries (NM 1)
  • Backend text (NM 1.5)
  • Backend sound (NM 1.5) <--> Radioswap?
  • Produce templates (NM 2)
  • TTS?

mid-March 2006


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.