Complejoweb

A style guide provides consistency throughout the handbooks, and offers guidelines for individual page structure, formatting, and markup, as well as for language usage, spelling, and capitalization.

All page submissions and edits must follow these guidelines. Updates to the handbooks submitted to the moderation queue will not be published until they conform to the Drupal style.

For a description of the Drupal handbooks, see the Handbooks overview.

For help with adding pages or editing pages, see the End user guide. All members of drupal.org can now create new pages in the handbooks. But when someone else updates a page you created, Drupal tracks that person as the page's author, and you lose ability to edit it. To update the page, either create a documentation issue that provides the update, or create an issue as a request to join the documentation team. When the request is approved, you will have permission to edit most handbook pages.

Embedded documentation (the Help system that is available within a Drupal site) has somewhat different style requirements. For more information, see the Embedded Documentation section.

A note about the documentation scope

New pages are always welcome, but please note that the scope of the Drupal handbooks is limited to the installation, management, use and development of Drupal along with the integration of Drupal with other software and services.

General information about web development, products, tools, software languages, standards, practices, techniques etc is considered out of scope unless the topic provides additional information which is specific to the Drupal environment. For example, a general tutorial on using CSS would be out of scope, whereas a discussion of how to work with CSS within a Drupal theme would be very much in scope. A procedure for installing Eclipse would be out of scope, whereas a procedure for configuring Eclipse for Drupal development work would be in scope.

Content that is beyond this scope may be removed.