GNOME Website Plan for 2.27/2.28
This page summarizes the GNOME website development plan for the GNOME 2.28 release which will be out on September 21, 2009.
Contents
-
GNOME Website Plan for 2.27/2.28
- Mission
- Scope
- Task forces
-
Schedule
- May 27 (Planning and Initial proposals)
- June 15 (Meeting, Monday, 21h UTC, #webhackers)
- June 17 (Content structure, final design, contenttypes, test website)
- August 10 (Meeting, Monday, 21h UTC, #webhackers)
- August 12 (Front page, About, Contact, Products and Download sections implemented, i18n prototype)
- August 26 (Support and Community sections implemented, i18n beta)
- September 7 (Meeting, Monday, 21h UTC, #webhackers)
- September 9 (General bug fixing)
- September 21 (Release of beta website)
Mission
Release a beta version of the new GNOME website featuring the reviewed content in a refreshed design using Plone as the underlying Content Management System (CMS).
Scope
For the 2.28 release, we'll be focusing on delivering a website containing:
- Front page
- About
- Products
- Download
- Support
- Community
- Contact
This is based on the previously proposed content for the website. There might be changes on the actual content of each of those items as they get reviewed by the Content team. This list represents the major topics which are essential for the first website release.
Our efforts should be directed towards getting those items done by the end of the 2.28 cycle. Any additions to the 2.28 scope should be explicitly proposed so that we avoid losing focus during the process.
Task forces
The project comprises three task forces with well defined goals: Content, Design, and CMS. Those task forces should work in parallel and integrate their work with each other when possible.
Content
Goal
Produce, scope, review and cleanup the new website content to get it ready to be released.
Guidelines
- Work in collaboration with Design team to deliver web content in an appealing format
- Clearly specify what graphics are needed to implement desired content on each website section
- Good communication with GNOME Marketing team in essential (to get volunteers, feedback, marketing direction, etc)
Members
- Jim Campbell
Status and Workspace at /Content
Design
Goal
Deliver a refreshed look and feel for the GNOME website to be implemented in the CMS.
Guidelines
- Work in collaboration with Content team to deliver web content in an appealing format
- Work in collaboration with CMS team to implement the new design in Plone in the most efficient way
Members
Status and Workspace at /Design
CMS
Goal
Implement a functional Plone instance using the new website design and content.
Guidelines
- Ideally, all implementation steps should be done with a respective documentation action on the GNOME wiki
- Focus on the specific scope of the 2.28 release
Members
- Carsten Senger
- Jens Klein
- Johannes Raggam
- Ramon Navarro
Status and Workspace at /CMS
Schedule
Each of those dates match a corresponding GNOME 2.27/2.28 development release.
May 27 (Planning and Initial proposals)
Goals
Content: Initial "mapping" of current content (list of things to remove, write, review, etc)
Deliverable: List of content items to be removed, reviewed or written sent to gnome-web mailing list
Design: Initial proposal of new website design in graphics form and call for comments
Deliverable: Send website design proposal to marketing-list in graphics format (png, svg, etc)
CMS: Sort out i18n solution for the website
Deliverable: Technical plan for website i18n sent to gnome-web mailing list
CMS: Sort out implementation plan for the website front page
Deliverable: Document front page implementation on a wiki page
CMS: Final list contenttypes to be implemented for the 2.28 release
Deliverable: Final list of contenttypes to be implemented documented on wiki with status information on each one (what's done, what's missing, etc)
CMS: Specify deployment requirements for GNOME servers
Deliverable: Requirement spec sent to gnome-web mailing list and published in a wiki page
June 15 (Meeting, Monday, 21h UTC, #webhackers)
June 17 (Content structure, final design, contenttypes, test website)
Goals
Content: Final proposal of content structure
Deliverable: New content structure documented on wiki
Design: Final website design ready to be implemented
Deliverable: Send final website design to gnome-web mailing list in HTML/CSS format
CMS: All contenttypes implemented
Deliverable: sample content for each implemented contenttype (page, image, news, etc)
CMS: Initial front page implementation
Deliverable: Non-styled front page with news, intro text, banner placeholder
CMS: Test website setup in GNOME servers
Deliverable: Test website with nightly builds running on website-test.gnome.org
August 10 (Meeting, Monday, 21h UTC, #webhackers)
August 12 (Front page, About, Contact, Products and Download sections implemented, i18n prototype)
Goals
Content: Front page, About and Contact content done
Deliverable: Final text/graphics for front page, About and Contact sections implemented in Plone
Content: Products and Download content done
Deliverable: Final text/graphics for Products and Download section
Design: Support CMS team on implementing the design on Plone
Deliverable: Help CMS team on applying the HTML/CSS on the Plone theme
Design: General design polishing
Deliverable: Design missing icons, graphics, and CSS required by the defined content
CMS: Front page implemented with new design
Deliverable: Front page implemented with new design in Plone
CMS: Prototype of website i18n implementation
Deliverable: Initial (possibly buggy) version of the i18n implementation with po file import
CMS: Products and Download implementation done
Deliverable: Products and Download section implemented in Plone
August 26 (Support and Community sections implemented, i18n beta)
Goals
Content: Support and Community content done
Deliverable: Final text/graphics for Support and Community section
Design: General design polishing
Deliverable: Deliver missing icons, graphics, CSS, etc. required by the defined content
CMS: Beta website i18n implementation
Deliverable: Beta version of the i18n implementation with po file import
CMS: Support and Community section implementation done
Deliverable: Support and Community section implemented in Plone
September 7 (Meeting, Monday, 21h UTC, #webhackers)
September 9 (General bug fixing)
Goals
Content: Review and increment content, general bug fixing
Design: General design polishing
CMS: General bug fixing in Plone instance
September 21 (Release of beta website)
Goals
Content: Review and increment content, general bug fixing
Design: General design polishing
CMS: General bug fixing in Plone instance