Table of Contents
How to use this Documenation WIKI
A brief description of how you use and contribute to this portal.
(This will be updated soon).
Welcome to the Help Center! This way of doing documentation is a bit different from what you may be used to, so please read this document to understand how to contribute.
For the impatient, here's the bare minimum you should know:
- You normally need to be logged in.
- There are several different documentation types, most are self-explanatory, but pay attention to the difference between a How-to and a Tutorial (explained below).
- To add a piece of documentation/help, go into the relevant section, make sure there isn't already an existing entry about what you want to add, and use the button at the top right to add (normally says Add FAQ or similar).
- Add your content, and save it. This edit/view cycle can be performed as many times as you like, until you are happy with the result.
- Make sure you Submit your document for publication when you are done - top right pulldown in the content area.
- A reviewer will then pick up the document, and publish it unless the content needs to be improved.
- If somebody adds comments to your entry later, you will be notified by e-mail.
What type of item is my documentation?
Below is a description, usage and example for each type.
Frequently Asked Question (FAQ)
An FAQ is a short question with a 1-2 paragraph answer. You can add several questions to a FAQ area and group the questions into sections::
FAQ Example Question: What is Plone? Answer: Plone is an open source Enterprise Content Management System (ECM/CMS) that runs on top of Zope and CMF.
A HowTo is a one-page description on how to accomplish something, but is folderish, so Files/Images can be attached. It's usually very brief and to-the-point.
- How to set up Plone with the Apache Web Server
- How to change the tabs that appear at the top of the portal
A tutorial is a multi-paged article with lots of detail. The tutorial is more in-depth than a How-to, and may cover the conceptual aspects of the task, in addition to the practical steps to get the job done.
If you are unsure of the difference of a How-to and a Tutorial, think about it as the difference between a recipe that only teaches you what ingredients are needed, and how to bake the cake (How-to), and an article telling you about the history behind cakes in general, that may or may not teach you how to actually bake one (Tutorial).
- How to utilize workflows in your projects
- Why separate content, logic and presentation?
An error reference is meant to be the explanation of a particular error, with details on how to fix it, if relevant.
Typical Error References
- Expected sequence, got integer
- FS Page Template has errors: Compilation failed