[Please collaborate and edit. This is meant to start as a brief analysis of the current system, angling towards a content brief for how a Drupal.org community content strategy should emerge going forward. The content audit will reveal shortcomings of the existing content.]
Why?
Drupal.org wants to grow and attract new users and open source contributors, as well as keep existing contributors productive and motivated.
The better plan for creating, planning, and governing content through its lifecycle will help keep content on drupal.org relevant and useful.
- help users get to the information they seek (general information, docs, issue queue, forums, groups etc.)
- set positive examples for current potential contributors
- demonstrate the awesome capabilities of Drupal software
- enable contributors to identify areas they can contribute to, based on their skills and interests
Who?
Drupal.org seeks to attract
- developers
- Visual and UX designers
- business owners
*content editors - new contributors
When?
Content on Drupal.org is constantly being created and edited in the form of issue queue comments and documentation. Drupal.org will ideally have an editorial calendar for non-technical communication.
Guidelines will be established for when content is considered outdated, and can be 'retired' so it no longer appears in search results or clutters the interface. (The exact meaning of retired will vary depending on the type of content).
A content audit is currently underway, and going forward, sections of the site could get periodic audits.
What?
- Drupal.org has a style & editorial guide that needs to be incorporated fully into Drupal.org site, and modified to include more criteria, as they are identified.
- front-page posts, community initiatives, community spotlights and other non-technical communication will be given the prominence they need.
- Written communication will be in a voice consistent with the editorial guide
Where?
The content strategy that will emerge will be adopted for the main Drupal.org site content first. If other subdomain organizers want to adopt it, that would also be great.
How?
(Good question!!! Volunteers periodically maintain content and look at Google Analytics. There is no content producers or director of marketing. There are no declared content leaders other than for the Docs team. Is this sustainable, or should other parts of the site have declared leaders?)