This page is the hub for the Drupal.org Redesign Content Migration. This is a wiki page for a reason - please add to and edit the page as needed. [last updated 2 August 2010 -- lisarex]
Overview
A big part of the redesign includes having new content on drupal.org.
Not all content will be nodes and blocks; some "page" content will be tpl.php pulled from the drupalorg.org module. Content issues will be tracked in the Redesign issue queue. Use the section components over the Content component whenever possible, so the section implementers are aware that content is being updated.
The initial focus will be on the main ~24 landing pages for the site, as listed on the Prototype page. Lisa and other volunteers have created a content inventory of the new content on Google docs. Get in touch if you'd like access to this.
Integration Site
The staging site at http://drupal:drupal@redesign.drupal.org/ will serve as the QA location, but it cannot be edited directly. Edits must be made on d.o or in code.
The Staging site now gets regular dumps from d.o and and from the d.o. customization code.
Content Migration Process - Simple Blocks and Nodes
- If you have permissions: Edit existing drupal.org nodes and blocks on the live site, or create new nodes and blocks on d.o., but don't publish them
- If you don't have permissions: post links and any content updates into the issue you've chosen to work on (or have been assigned to)
- If you have permissions: Create a new issue for every new node/block/content that has been created (or undergone major revision) in the Redesign issue queue
- The published content will be deployed to integration on the next deploy OR the developer can also create it on integration with the understanding it will be overwritten on the next dump. Unpublished content will be integrated later.
- If you don't have permissions: Lisa, Neil or someone else will review, incorporate the changes, and save them
Content Migration Process - Code (templates, Views, or drupalorg.org module
- Anyone with a BZR checkout of the drupalorg code base can create a patch and post the patch to the Redesign issue queue so it can be reviewed and committed via CVS
- Once committed, the patch will be pushed to the integration site
- Anyone who who needs help or doesn't know how to put changes into code and create a patch should ask us for help.
Content Modification Guidelines
The Redesign includes new perspectives on how Drupal.org content is organized and displayed:
- Less is more. Edit for clarity and conciseness.
- Lengthy content may be better served by breaking the content into several sub-pages.
- Replace outdated information with newer information
- Follow the Drupal User interface best practices
- And also follow the style guidelines: https://infrastructure.drupal.org/drupal.org-style-guide/editorial.html
- Page need to follow SEO best practices, including a clean URL
How to Get Involved
Lisa Rex and the implementers will be involved in migrating content, but we can always use more help! If you wish to assist, follow these steps:
- Read the Redesign Project Overview
and use the included instructions to contact the association using the "Implement part of the drupal.org redesign" category. - Create a Drupal.org account (if you don't have one already)
- Sign up for the Redesign Group (if you haven't already)
- Read the Implementers Guide
Related Links
Issue Queue - Task Tracking and Assignments
Tasks are tracked and assigned using the project's Issue Queue with the Component "Content Migration"
Implementation Team
The list of people working on Content Migration is maintained on the Assignments and Contact Info page.
SEO Guidelines
As we modify pages, we need to adhere to the SEO Guidelines.
Use the Keywords tool guidelines for guidance in selecting keywords.
Advice on writing a good Title tag is available.
CSS Guidelines
Follow the CSS Guidelines
Markup Guidelines
Some information about appropriate use of HTML markup on the site