FLUID-708: Determine left sidebar navigation

Metadata

Source
FLUID-708
Type
Sub-task
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Jonathan Hung
Reporter
Jonathan Hung
Created
2008-06-04T10:54:09.000-0400
Updated
2011-03-17T15:06:05.654-0400
Versions
  1. 0.3
Fixed Versions
N/A
Component
  1. Infrastructure

Description

Review the left sidebar navigation and rearchitect to be more relevant.

  • improve categorization
  • reorganize navigation to be more relevant
  • What should be prominent? What shouldn't?

Comments

  • Jonathan Hung commented 2008-06-06T12:33:11.000-0400

    Update June 11: This proposed navigation structure has been replaced.

    Proposed new navigation scheme for left sidebar:

    1) Project

    • project description
    • aims and goals *
      • initiatives (OSDPL, VULab, UX Toolkit, etc)
    • disciplines involved (UCD etc)
    • Questions / Help *
      • technical
      • design
    • Contact us

    2) Community

    • Current work (Who's doing what)
    • How to Contribute *
      • list of tasks
    • Discussions *
      • meetings
      • mailing lists
      • IRC
      • IM
    • Directory (Who's who - Who can I ask questions of...) (TASK)

    3) Knowledge Base

    • FAQ (FLUID-709)
    • design
    • implementation / development
    • UX
    • security
    • project coordination *
      • Road maps etc.

    4) Fluid Components

    • download
    • source code
    • designs
    • documentation *
      • user manual
      • release notes
    • online demos (demos, daily builds) (FLUID-710)
    • current components
    • future components

  • Jonathan Hung commented 2008-06-11T12:12:30.000-0400

    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
    • release notes (release pages for various releases, should also
      contain link to manual)
    • source code (links to SVN, and different bundles)
    • designs (design patterns, designs for current and upcoming components)
    • user manual (how to install, run, test, integrate Fluid components)

    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
    • current work (will include link to planned future work)
    • how to contribute
    • disciplines (may be moved into Knowledge Base - UX/Design section)
    • discussions (points to Mailing lists, Breeze, IRC, IM, also Meetings)
    • Contributor directory (hopefully some content to be automatically
      pulled from Wiki profile pages)

    About Fluid

    • aims and goals
    • contact us