Waldemar Kornewald wrote:
On 9/30/06, Michael Phipps <mphipps1@xxxxxxxxxxxxxxxx> wrote:It's sort of funny - we had almost these exact conversations back when we built the last site. How do we arrange all of the data? What menu headers do we use? What sorts of people will visit the site? :-)
So, it's not an easy topic. ;)
No. It wasn't then, and it isn't now.
That's why I would propose a menu structure (with quality ascii art!) like
this:
Developer | User | Community | Corporate ---------------+------------------+---------------------+------------ HaikuBook | Tutorials | Forums | About Us Tutorials | Users Guide | Links | Donate Build Fact. | HW Compatibility | Bug Tracker | Contact Us Code Tutor'l | Newsletters | Banners/Buttons | Marketing Code Guideln | FAQ | Associated Projects |
I have the impression that this step only introduces an improvement for developers, but it won't change a lot for end-users. I think we can achieve the same by adding a "Development" menu tree to the navigation block (where you have "logout", etc.) or by adding an extra menu block for development links (always visible).
I've setup a similar menu structure, so we can directly compare the two navigation schemes. BTW, for the final site we should probably have the navigation block on the left and "Similar entries", etc. on the right, so the navtree is more accessible.
I still don't quite see why we would want a wiki. We could easily add a tips section under user or community that people could submit to.
How can people submit questions without answers, then? Should we have create a "Put your questions here." page and use comments to ask and answer questions (and later move interesting, answered questions to a separate page)? Is that open enough? A wiki would at least allow for everyone to directly make these edits.
