Platform/GFX/DesignDocumentationGuidelines: Difference between revisions

Line 23: Line 23:


* Name the documentation file appropriately, use the .md extension (assuming it is markdown, and if not, why not?)
* Name the documentation file appropriately, use the .md extension (assuming it is markdown, and if not, why not?)
* Use the markdown syntax (and if not, why not?)
* Use the markdown syntax (and if not, make sure you understand why not)
* Put \page alllowercasenameofthefile at the top
* The source file could/should contain a pointer to the documentation, and vice versa.
* The source file should contain a pointer to the documentation, and vice versa.
* The documentation file may reference classes or files themselves:
* The documentation file may reference classes or files themselves:
** mozilla::gfx::SomeClass
** mozilla::gfx::SomeClass
Line 32: Line 31:
** SomeClassFile.h
** SomeClassFile.h
* The source (or other external files) may reference the documentation file:
* The source (or other external files) may reference the documentation file:
** [this way](@ref alllowercasenameofthefile)
** [this way](@ref SomeExternalFile.md)
** just by name as SomeExternalFile.md
* Good because:
* Good because:
** The documentation is versioned
** The documentation is versioned
Confirmed users
564

edits