dev-guide:markdowndoku
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dev-guide:markdowndoku [2024/07/05 11:55] – timOb | dev-guide:markdowndoku [2024/07/08 10:50] (current) – timOb | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| + | |||
| + | With GroIMP 2.1.4 it is possible to use a markdown file to generate the content of the embedded documentation of a GroIMP plugin. The idea is that the README.md file of a git repository is then doubly used. Yet since the pipeline depends on pandoc, it is in theory also possible to use a [[https:// | ||
| + | |||
| + | |||
| + | ===== Requirements ===== | ||
| + | |||
| + | To use this pipeline it is required that pandoc is installed, and that the project contains the files | ||
| + | template.docbook and copyfilter.lua in the directory '' | ||
| + | |||
| + | |||
| + | ===== Enabling/ disabling the pipeline ===== | ||
| + | |||
| + | By default this pipeline is disabled, since parts of GroIMP contain docbook based documentation. To enable it for a certain plugin the maven property " | ||
| + | |||
| + | <code xml> | ||
| + | < | ||
| + | | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | To disable this pipeline the same property must be deleted or set to " | ||
| + | |||
| + | |||
| + | |||
| + | ===== Selecting a source ===== | ||
| + | |||
| + | The source of the pipeline is by default " | ||
| + | |||
| + | <code xml> | ||
| + | < | ||
| + | | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | At this position it would also be possible to set other formats e.g.: '' | ||
| + | Moreover it is possilbe to set several files (only markdown) as a parameter, this files then will be concatenated and process as one and create one docbook file: ''< | ||
| + | |||
| + | |||
| + | ===== Markdown Syntax (GroIMP flavored Markdown) ===== | ||
| + | |||
| + | The markdown flavor used here is the one of pandoc with only a very few additions: | ||
| + | |||
| + | |||
| + | ==== Images ==== | ||
| + | |||
| + | To ensure that images included in the file are shown in the readme.md on Git as well as in the embedded documentation, | ||
| + | |||
| + | To scale an image in size please use:'' | ||
| + | The content of [Lable] is then in the documentation used as the the label of the image. | ||
| + | |||
| + | |||
| + | ==== In GroIMP references ==== | ||
| + | |||
| + | If the documentation is about a certain panel, option or example, it is possible to create a hyperlink in GroIMP that shows this resource. This works based on the ' | ||
| + | |||
| + | To ensure that this links do no weirdly show up on the Readme in the git the following syntax can be used. | ||
| + | |||
| + | < | ||
| + | *panels/ | ||
| + | *examples: | ||
| + | *preferences: | ||
| + | </ | ||
| + | |||
| + | This will, on git, only show the paths in italic. For GroIMP it will be preprocessed to create the links to the commands to present the requested resource. | ||
| + | |||
| + | |||
| + | ==== Tables ==== | ||
| + | |||
| + | to add a table the the following syntax can be used: | ||
| + | |||
| + | < | ||
| + | | header 1 | header 2 | header 3 | | ||
| + | | --- | --- | --- | | ||
| + | | cell 1 | cell 2 | cell 3 | | ||
| + | | cell 4 | cell 5 is longer | cell d | | ||
| + | | cell 7 | ||
| + | |||
| + | </ | ||
| + | |||
| + | |||
| + | ==== Defining the title ==== | ||
| + | |||
| + | By default the title of the chapter of documentation is the name of the plugin in the maven pom. | ||
| + | This name can be change by adding the variable " | ||
| + | |||
| + | < | ||
| + | --- | ||
| + | ftitle: GroIMP user manual | ||
| + | ... | ||
| + | |||
| + | </ | ||
dev-guide/markdowndoku.1720173316.txt.gz · Last modified: 2024/07/05 11:55 by timOb
