en:dev:howto:module
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:dev:howto:module [2014/06/14 07:42] – created nerdoc | en:dev:howto:module [2017/10/16 13:22] (current) – typo nerdoc | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{tag> | ||
| ====== How to write a new module ====== | ====== How to write a new module ====== | ||
| + | |||
| + | As there is no code at the moment, there is still no information available how to actually **write** a module. But at least it is avaliable how to write documentation/ | ||
| ===== Write documentation ===== | ===== Write documentation ===== | ||
| Add a new page for the module here to wiki. Modules each have their own namespace, because each module can be very different to others, so it's better to keep them separated. | Add a new page for the module here to wiki. Modules each have their own namespace, because each module can be very different to others, so it's better to keep them separated. | ||
| - | So e.g. the '' | + | So e.g. the base description of the '' |
| + | |||
| + | * Every module should provide information about dependencies to other modules, a detailed (technical) description what is the **purpose** of the module, which **responsibilities** it has and how it is **structured**. | ||
| + | * Every module has a '' | ||
| + | * A '' | ||
| + | * The page should also contain a link to the API of the module, which should be available automatically after the code is properly documented using sphinx/ | ||
| + | |||
| + | FIXME Maybe Spec/API should be together, using Sphinx... | ||
| + | |||
| + | If you set up a new module page (by creating the new page '' | ||
en/dev/howto/module.1402724546.txt.gz · Last modified: 2014/06/14 07:42 (external edit)