END OF NEW CONTENT
(old content for refactoring)

Please read (and follow) these standards. You should also read about our documentation goals.

• Page: In the Tiki documentation, the term page is synonymous with wiki page.
• Feature: A feature is a Tiki component that has a distinctive function, such as image galleries, file galleries, FAQs, banners, forums, or blogs. See Features for an overview of Tiki features.
• Terminology: Review the Tiki Glossary for additional standard Tiki terminology.

All documentation pages are integrated into a wiki structure.

• Standards
  For examples, see Documentation Templates.
  Every page should uniformly follow the Tiki Manual of Style as applied in Requirements, for example.
• Status
  The Documentation Status is the hardcoded and commented version of the structure. If you add new pages, please add them with a visible indication TO CREATE so they can be added to the structure. Cleaning and page moving will occur frequently.

Each feature requires at least four pages of documentation.

• Main Page
  Example Main Page: Blog
  This is the primary page for the feature and should be named based on the feature. It defines and provides a brief overview of the feature. The page should link to any related resources (internal or external).
• User Help
  Example User Page: Blog User
  This page is for end-users of the feature, this also includes Admins who use their own sites. Organize the User page by tasks — what the user wants to accomplish (such as "Creating a New Blog" or "Preventing Other Users From Posting"). Use lots of screenshots and graphics to convey the information.
• Admin Configuration
  Example Admin Page: Blog Config
  This page provides information that Admins need in order to enable, configure, maintain, and troubleshoot the feature. Include system requirements information, potential impact to other features, or anything else useful to a system administrator.
• Reference
  Example Reference Page: Blog Ref
  This is page is for additional reference documentation. It includes the following information:
  • Permissions relevant to the feature
  • Pertinent database tables
  • Administrative configuration options
  • User options

ML: This idea can be ok for certain large features, but it's overkill for the vast majority of features that should fit on one page. Let's not create pages artificially to try to fit the content into a structure.

If you're registered and logged in, you can get started:

1. Choose a topic or feature
   From the Documentation Status page, choose a feature to document.
2. Find existing content
   Review http://tiki.org to see if documentation exists for the feature. If so, copy it to this site and reformat it, as necessary.
   You may also want to review the old 1.6 TikiWiki documentation for additional information.
3. Write what is missing
   Create or update the page so that it conforms to the formatting standards. Review the documentation examples for additional information, including sample pages.
4. Work collaboratively
   Update Documentation Status so that other contributors know what you're working on (and what still needs to be done).