17
edits
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Writing Documentation with the Add-ons Builder SDK | |||
== Writing Documentation with the Add-ons Builder SDK == | |||
Documentation in the Jetpack SDK is a self-contained system; it is dynamically built based on the files contained within the structure of the SDK. The javascript lives in jetpack-sdk/packages/<package-name>/js the corresponding documentation lives in jetpack-sdk/packages/<package-name>/docs. As long as the prefix for the .js and the .md files is the same, the documentation will be generated and viewable via the "cfx docs" command. | Documentation in the Jetpack SDK is a self-contained system; it is dynamically built based on the files contained within the structure of the SDK. The javascript lives in jetpack-sdk/packages/<package-name>/js the corresponding documentation lives in jetpack-sdk/packages/<package-name>/docs. As long as the prefix for the .js and the .md files is the same, the documentation will be generated and viewable via the "cfx docs" command. | ||
| Line 7: | Line 9: | ||
APIDocs This has roots in the JavaDocs 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. [reference a JavaDocs site] | APIDocs This has roots in the JavaDocs 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. [reference a JavaDocs site] | ||
A Short, Well Documented Example | == A Short, Well Documented Example == | ||
Properties | Properties | ||
| Line 37: | Line 40: | ||
Further examples can be found in the jetpack-core/docs directory. | Further examples can be found in the jetpack-core/docs directory. | ||
Submitting changes/updates to jetpack-core Documentation | |||
== Submitting changes/updates to jetpack-core Documentation == | |||
Found something that we're missing? Bugs? Additions? In order to contribute to the jetpack-core docs, please follow the following process to get your changes submitted successfully. | Found something that we're missing? Bugs? Additions? In order to contribute to the jetpack-core docs, please follow the following process to get your changes submitted successfully. | ||
| Line 51: | Line 56: | ||
5. When the change is approved, it will be submitted to the trunk by an appropriate engineer. | 5. When the change is approved, it will be submitted to the trunk by an appropriate engineer. | ||
== Writing Docs For Your Own Modules == | |||
As you continue developing with the Add-ons Builder SDK, you may want to include documentation with your own modules. | As you continue developing with the Add-ons Builder SDK, you may want to include documentation with your own modules. | ||
edits