Lets talk about style!
PageLines, like yourself, has it's own style. This page will discuss how to keep this style consistent in all the pages in the Docs.
Conversational. Write like you would talk. No one wants to read another dry software manual. Keep it technical but be upbeat and fun when appropriate.
Avoid using 10 words when 3 will do. Keep it concise and it will communicate better.
PageLines belongs to the community, tell it that way. Use PageLines instead of 'I, we, our" its not them vs us its all of us!
When using PageLines on WordPress to do screenshots and videos for the Docs, please use a clean, localhost install of PageLines on WordPress. All settings should be reset to default in-between writing new How-Tos.
There are two main categories of articles.
This is a simple definition of the term.
All Glossary items will be organized in alphbetical order on the Glossary page.
If your definition gets long enough to use a table of contents, it's probably not a definition. Keep it clear and concise.
This is an in-depth walkthrough of how to use a specific function or complete a task using PageLines.
How-tos will consist of a text walk-through with supporting images.
The walkthrough should also be available as a video in as many cases as possible.
When referencing the use of tools like FTP clients or CSS editors. Reference the section on the [[Tools]] page rather than the tool itself. All suggested tools should be included and described on the Tools page.
The first header inside of any page should be an h2 header using ==Header==. Single = signs are reserved for the page title only.