FLUID-763: Implement new navigation structure

Description

Through a series of emails, the following 3 Primary audiences are going to be targeted (listed in priority):

1. lurker (someone new who wishes to learn more about the project)
2. contributor (someone who wants to help with the project)
3. implementor (someone who wants to use Fluid in their own software)

The navigation will be restructured to meet the needs of the above 3 parties. The following is the proposal:

Fluid Components

• downloads and demos (FLUID-764)
• source code (links to SVN, and different bundles FLUID-765)
• designs (design patterns, designs for current and upcoming components FLUID-767)
• user manual (how to install, run, test, integrate Fluid components FLUID-754)

Knowledge Base (this category seems a bit ambiguous now – see question above)

• user experience (other wiki pages related to design and UX)
• development (other wiki pages related to development)

Community

• meetings (FLUID-770)
• current work (will include link to planned future work)
• how to contribute (FLUID-771)
• disciplines (may be moved into Knowledge Base - UX/Design section)
• discussions (points to Mailing lists, Breeze, IRC, IM, also Meetings) FLUID-772
• Contributor directory (hopefully some content to be automatically
  pulled from Wiki profile pages)

About Fluid

• aims and goals
• contact us

Iteration12

Comments

• Jonathan Hung commented 2008-06-11T12:27:53.000-0400

  I suggest that this be one of the last tasks we do in the restructuring. Start with creating the content pages first then create the navigation at the end.

• Jonathan Hung commented 2008-07-03T20:46:02.000-0400

  For the most part this is completed. Missing some items from the navigation, but I think it works.