| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This collects all release steps in a release-checklist template.
|
| |
|
|
|
|
|
|
|
|
|
| |
This adds the Contributing Tutorial (contributing-tutorial.md) to
the pages setting of Mkdocs, so that the tutorial will render
in the readthedocs.io documentation.
Closes: #1711
Approved by: jlebon
|
|
|
|
|
|
|
| |
This adds detailed information on commit message guidelines, a link to the contributing tutorial, and minor typo fixes.
Closes: #1694
Approved by: cgwalters
|
|
|
|
|
|
|
| |
Signed-off-by: Chen Fan <fan.chen@easystack.cn>
Closes: #667
Approved by: cgwalters
|
|
|
|
|
|
|
|
| |
The link for git-rebase manual contains stray character (])
at the end.
Closes: #592
Approved by: jlebon
|
|
|
|
|
| |
Closes: #230
Approved by: jlebon
|
|
|
|
|
|
|
|
|
|
|
| |
I was going through the new version of the docs and noticed a few
problems. Mostly URLs that aren't linked, extra whitespace, and a few
mis-spellings.
I ran the files through `aspell check` and made some manual changes
myself.
These changes were tested locally with `mkdocs serve`
|
|
I don't much like Docbook (and am considering converting the man pages
too), but let's start with the manual.
I looked at various documentation generators (there are a lot), and
I had a few requirements:
- Markdown
- Packaged in Fedora
- Suitable for upload to a static webserver
`mkdocs` seems to fit the bill.
|