Labs/Site 2.0/Existing site replacement/Details
From MozillaWiki
Goals
Replace the existing labs site + labs project pages with a system that...
- Removes technical bottlenecks in updating the site
- Helps to grow the Labs community
Requirements
- Creating new project sites cannot require SVN, and should be as fast and easy as possible.
- There should be a default look and feel for all new project sites, but these must also be customizable on a per-project basis.
- Adding or updating content on the Labs site must not require SVN and should be possible using a Web UI.
- Automate the updating of content on project sites as much as possible so as to reflect current project activity (ie: through pulling in RSS feeds for discussions, bug reports, blog posts, etc.).
- It must be clear to potential users how they can obtain and test the software as well as ask questions, get support, and file bugs.
- It must be clear to potential designers and developers how they can get involved with the project.
- Each project needs its own weblog.
- Each project needs its own RSS feeds.
- Must support a unique look and feel for each project.
- Project blogs must support all the same features as Wordpress -- categories, tags, various feeds, etc.
- Must be able to add pages to project sites without requiring SVN, ideally through a Web UI.
- Different users will need different permissions for various project sites/blogs. User permissions cannot be universal for all projects/blogs.
- Main Labs blog should have a Planet-like system for pulling in all Labs-related sites/blogs.
- Each project blog should optionally have a Planet-like feature for all project-related sites/blogs.
- Each project site must provide links for downloading (where appropriate), documentation, user-support, bug reporting, etc.
- Each project site should clearly reflect and point to recent activity related to the project (bugs filed, discussions, blog posts etc.).
- Each project site should clearly reflect the current status of the project -- active, archived, etc.
- It must be easy for users to get the information they need to obtain and test whatever software is available.
- It must be easy for potential developers and designers to find out how to get involved with the project.