17
edits
Jetpack/SDK/Writing Documentation: Difference between revisions
Jump to navigation
Jump to search
m
Jetpack/SDK/Writing Documentation (view source)
Revision as of 20:44, 18 August 2010
, 18 August 2010→Writing Documentation for the Add-ons Builder SDK
| Line 2: | Line 2: | ||
== Writing Documentation for the Add-ons Builder SDK == | == Writing Documentation for the Add-ons Builder SDK == | ||
Documentation in the Jetpack SDK is a self-contained system within the SDK itself. All of the documentation is generated on the fly, via actual files located in the directory structure | Documentation in the Jetpack SDK is a self-contained system within the SDK itself. All of the documentation is generated on the fly, via actual files located in the directory structure. SDK documentation is viewable either as source (at any time) or as a web page after the SDK has been activated and the "cfx docs" command has been run from the command line. | ||
The "cfx docs" command launches a small web server in order to render the documentation for human consumption. It relies on three things: | The "cfx docs" command launches a small web server in order to render the documentation for human consumption. It relies on three things: | ||
* That the documentation is written in Markdown syntax | * That the documentation is written in Markdown syntax | ||
* That the API component is | * That the API component is described in APIDoc syntax | ||
* That there are corresponding .js/.md files in the lib/docs directories (e.g. tabs.js/tabs.md) | * That there are corresponding .js/.md files in the lib/docs directories (e.g. tabs.js/tabs.md) | ||
All documentation for Jetpack(s) | All documentation for Jetpack(s) should be written using these three tools. | ||
| Line 16: | Line 16: | ||
=== On | === On APIDoc Syntax === | ||
This has roots in the JavaDoc format for documenting APIs within the structure of the Java code itself. The idea was to make it functionally similar to document APIs within the code as well as provide a way to give a framework for documenting the API in a human-readable format. An overview of JavaDoc format on [http://en.wikipedia.org/wiki/Javadoc wikipedia]. | This has roots in the JavaDoc format for documenting APIs within the structure of the Java code itself. The idea was to make it functionally similar to document APIs within the code as well as provide a way to give a framework for documenting the API in a human-readable format. An overview of JavaDoc format on [http://en.wikipedia.org/wiki/Javadoc wikipedia]. | ||