developer.jelix.org is not used any more and exists only for history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Changes between Version 1 and Version 2 of en/doc-guidelines


Ignore:
Timestamp:
Jun 21, 2009, 7:45:50 PM (11 years ago)
Author:
afroxav
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/doc-guidelines

    v1 v2  
    11= Documentation Guidelines =
    22Here is a summary of the guidelines for the english documentation. You are free to apply or not these guidelines in the other language.
     3
     4== General writing ==
     5There is simple trick that you use when writing documentation. You need to make sure that the content is reader-friendly, so avoid putting to many technical terms: don't talk about Unix sockets when talking of database, even if they are mentioned in the API. Write your documentation as if the reader remember only half of what he read on the preceding pages, but remembers everything from the current page. Be mindful, and don't over-simplify the documentation: advanced users won't like it.
     6
     7As always, be careful for grammar and spelling mistake. Write in regular, international english and don't use colloquial terms. Always preview your changes, to double check for errors.
     8
     9== Inline code ==
     10There are many guidelines for inline code. However, following them will create a consistent look in the documentation
     11
     12=== Files and folders ===
     13For files and folders referenced inside text, use the inline code syntax. You simply add @@F@ before the path and @@ after.
     14{{{
     15@@F@The/path/of/the/file.php@@
     16}}}
     17
     18=== Function names ===
     19To specify a function name inside a paragraph, surround it with **.
     20{{{
     21**jelixClass::function**
     22**function** of the jelixClass
     23}}}