So lets say we do it

[Dimitrie O. Paun]

On October 31, 2002 07:00 pm, Francois Gouget wrote:

This is a good start. Here are my comments, based on
the following principles:
  -- while I appreciate (as a geek) the logical nesting
     of topics, I think they should be organized
     more around usage patterns. A common topic should
     be accessible with one click, a obscure one, with two.
  -- keep things simple, for areas that are of general use
     (i.e. used frequently by non-developers)

> 1. About
>   1.1. Intro
>   1.2. Why Wine
>   1.3. Wine myths debunked
>   1.4. Technical details
>   1.5. Status (or move this to the How to contribute or Development
> section?)

I think this one should be top-level. I was fascinated for a long
while by http://www.gnustep.org/information/progress.html, and
I kept visiting the site frequently to monitor their progress.

>   1.6. History
>   1.7. Alternatives
>   1.8. Who's who

BTW, this one needs updating *badly*.

>   1.9. Wine companies
>   1.10. Community
>   1.11. Contacts
>   1.12. Legal

This menu should show as "About" on top level, and when clicked,
should expand to the above structure. This is because it's long,
and the items here (apart from Status) don't merit front-page
status.

> 2. News
>   2.1. Latest Wine release
>   2.2. Latest WWN
>   2.3. WWN back issues
>   2.4. Press

Hopefully we can fit all this in one page, with a clever 1,2 box
layout, and we can drop the submenus.

> 3. Screenshots
>    General screenshots, typically full desktops. Also point people to
> the Application Database.
>
> 4. Application Database
>
> 5. How to contribute
>   5.1. Application maintainer
>   5.2. Bug triage
>   5.3. Web site maintenance
>   5.4. Development
>      5.4.1. Wine 0.9.0 task list
>      5.4.2. The Tasklist (bug 395)
>      5.4.3. The FIXMEs (bug 455)
>      5.4.4. The Tasklets (bug 406)
>      5.4.5. The most wanted bugs (a Bugzilla query returning bugs with
> the most votes)
>   5.6. Write regression tests
>   5.5. Support Wine-based products

This should expand as "About" on click only. The 5.4.x items are a bit
too deeply buried, considering that they are high visibility. Maybe
we can link to 5.4 from the Status page. Or even better, maybe we can
make 5.4 a top-level item, and rename it "Todo".

> 6. Download
>   6.1. Binary Packages
>   6.2. Source tar files
>   6.3. Source tars for CVS
>   6.4. LXR
>   6.5. CVS
>   6.6. CVS Web
>   6.7. Other CVS modules (web site)

Too complex. I think only 6.1, and 6.2 belong here, and not as
submenus, but part of the page. The rest should be moved under 7.

> 7. Development
>   7.1. Mostly references to the Wine Developers Guide which is where
> most of the information should be.
>        The distinction between this and the Wine Developers Guide is
> that the guide should be more about general principles and less about
> which specific web server to connect to (although that's more a download
> issue anyway).
>   7.2. References
>       Pointers to online resources (Win32 documentation, X doc, etc.)
> useful to Wine developers.
>
> 8. Documentation
>   8.1. User Guide
>   8.2. Howto
>   8.3. FAQ
>   8.4. Developer Guide
>   8.5. API Documentation
>   8.6. Packager Guide
>   8.7. How to get commercial support
>
> 9. Bugs
>    (Bugzilla)

What about this:

8. Support
  8.1 FAQ
  8.2 Howto
  8.3 Bugzilla
  8.4 Commercial support

9. Documentation
  9.1 User Guide
  9.2 Developer Guide
  9.3 Packager Guide
  9.4 API Docs

> 10. Forums
>   10.1. Mailing lists
>   10.2. Newsgroup
>   10.3. IRC channel

-- 
Dimi.