Plugin documentation files
There are three documentation files that can (and should) be created for a plugin.
The classic documentation file in markdown format, containing basic information how a plugin can be configured and used.
user_doc.rst / user_doc.md
The user_doc file can be created in restructured text (rST) or markdorn format. You should prefer the restructured text format because it is more feature rich. The user documentation should be written in German. Only it the plugin author does not speak German, the user documentation can be written in English. The reason for this is, that the user documentation is going to become multilingual at a later point in time and the translation source has to be one language.
This file is dynamically integrated in the user documention for SmartHomeNG when it is beeing built.
The first Heading of the user_doc.rst / user_doc.md or developer_doc.rst / developer_doc.md MUST be the short-name of the plugin in lower case.
It is used as the entry in the navigation bar of the documentation. Choosing an other top level header for these files would make the documentations navigation inconsistent.
The backend plugin has a file user_doc.rst. This file is integrated in the navigation tree of the user documentation. The entry can be seen, if the corresponding plugin category is selected:
When selecting the entry in the navigation pane, the page is displayed:
This page can contain images. The images should be stored in a folder named asstes within the plugin folder.
In restructured text (rST) files, the images can then be included by the statement:
.. image:: assets/<picture-filename>
developer_doc.rst / developer_doc.md
The developer_doc file can be created in restructured text (rST) or markdorn format. You should prefer the restructured text format because it is more feature rich. The user documentation should be written in English.
This file is dynamically integrated in the developer documention for SmartHomeNG when it is beeing built.
The visu_websocket and the visu_smartvisu plugins have pages for the developer documentation: