General guidelines to edit the documentation¶
It’s better for version control systems and diff tools to break lines at a sensible number of characters. Long lines appear as one diff. Also merging is more complex because merges are line based. Long unbreakable items may be longer (links, refs, …). We chose to use 160 chars.
Please indent all directive content by 3 spaces (not 2, and no tabs).
*as an itemize character, since
+are supported by docutils, but not officially supported by Sphinx`.
Please underline all headlines with at least as many characters as the headline is long. Following the Python pattern for headline the levels are:############ ************ (sometimes skipped in small documents) ============ ------------------- ‘’’’’’’’’’’’’’’’’’’’’’’’
It’s not required to write:samp:`code`
The default role for``…``
:samp:is only required when you want to write italic text in code text.
Now, variable becomes italic.
Please simplify all usages of
…`to `…`` for readability. Here are the regular expressions for an editor like Notepad++:
- Search pattern::
- Replace pattern::
Each backend has one folder and each platform/compiler has one file. Please note that page headlines are different from ToC headline:.. toctree:: :hidden: ToC entry <file1> file2
A documentation should not use “you”, “we”, …, because it’s not an interactive conversation or informal letter. It’s like a thesis, everything is structured and formal. However, to make it more friendly to newcomers, we agree to allow informal language in section ‘Quick Start Guide’.
Please keep errors low.
Guidelines to edit section ‘Building’¶
I prefer a text block, which explains how a compilation works, what I can configure for that backend, etc. After that, I prefer a code block with e.g. bash instructions on how to compile a backend. A list of instructions with embedded bash lines is not helpful. An experienced, as well as novice user, would like to copy a set of instructions into the shell. But it should be stated what these instructions will do. Complex flows like for GCC, can be split into multiple shell code blocks. Moreover, I find it essential, to demonstrate when and where to change directories.
We would like to see a list like
- gcc (Gnu Compiler Collection)
- gcc-gnat (Ada compiler for GCC)
- llvm-del (LLVM development package)
The goal is to also explain what a user is installing and what the few lines in the build description do. Now they know the name, can search for similar names if the have another package manager or distro or can ask Google/Wikipedia. We often find many build receipts with cryptic shell code and to execute this unknown stuff with sudo is not comfortable. We would like to know what it does before hiting enter.
genindex.htmlfrom the navigation bar. [#200]
Create “parts” (LaTeX terminology / chapter headlines) in navigation bar. [#200]
- Intersphinx files [#200]
To decompress the inventory file: curl -s http://ghdl.readthedocs.io/en/latest/objects.inv | tail -n+5 | openssl zlib -d. From how-to-uncompress-zlib-data-in-unix.
External ref and link to section:
:ref:`GHDL Roadmap <ghdl:CHANGE:Roadmap>`
External ref to option (no link):
The indentation of the elements in the side menu have been modified. They are fixed por levels 1, 2 and 3 (#294) and 4 (later).
The RTD menu (bottom-left) has been modified (#294):
- No headlines are shown. It is not possible to remove only one of them with CSS only (JS would be required). However, because the content in most of the lines is self-explained, it is preferred not to show any.
- The Search box is removed.
- Ubuntu uses dash instead of bash when a shell script is run. As a result, some functionalities, such as arrays like
array, are not supported. Therefore, build scripts in dist/linux should not use those functionalities unless they are sourced in a bash shell. That is,
tavis-ci.shuses arrays, since it is sourced in the Travis CI machine. But
buildtest.shdo not use any. The same applies to the scripts in testsuite.