...
- why: Why use OpenOffice.org
- download: Direct download specific product only
- support: Support area (many alternativisalternatives!)
- extensions: get extensions (housed at OSU)
- participating: catch-all for all kinds of particiaption
- news (top navigation bar): news, manually edited
- download: Complete download page (user, developer version, other information)
- projects (top navgiation bar): a complete listing of all projects
- people: registered OO.o participants (needed for mailing list activity, etc.)
- my page (participant login)
- about: a page about the project
...
- Once a new "site" is determined, what content tools (cms, standard headers/footers, server-side include templates, etc.) are available and who can access them?What will be contained on the initial structure/landing page do we want for this site?
- Can existing content can be ported over? And if so, how and who will do it?
- A flexible content management system must be available for this site outside the Apache "committer" process if at all possible.
Content Migration
Keep the following /pages areas with some editing as needed:
- why
- about (doesn't need to be a separate "site")
- download
- support (scale down this page...highlight forums and documentation)
- participate/contribute
- extensions
- native-lang pages
Project/Developer Site (openoffice.apache.org)
Questions
- What to do about "non-product development" projects?
- Should the developer arm take over direct involvement with the "mirrors" and "distribution" projects?
-- to be continued --
Other Sites/Services (especially OO.o wiki and extensions)
...