2023-07-25 17:56:42 +03:00
# Contributing to the Nixpkgs manual
2021-03-04 19:52:32 +03:00
This directory houses the sources files for the Nixpkgs manual.
You can find the [rendered documentation for Nixpkgs `unstable` on nixos.org ](https://nixos.org/manual/nixpkgs/unstable/ ).
2021-03-06 14:35:33 +03:00
[Docs for Nixpkgs stable ](https://nixos.org/manual/nixpkgs/stable/ ) are also available.
If you're only getting started with Nix, go to [nixos.org/learn ](https://nixos.org/learn ).
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
## Contributing to this documentation
2023-07-25 18:51:38 +03:00
You can quickly check your edits with `nix-build` :
```ShellSession
$ cd /path/to/nixpkgs
$ nix-build doc
```
If the build succeeds, the manual will be in `./result/share/doc/nixpkgs/manual.html` .
2023-08-14 05:36:45 +03:00
### devmode
2023-07-25 18:51:38 +03:00
The shell in the manual source directory makes available a command, `devmode` .
It is a daemon, that:
1. watches the manual's source for changes and when they occur — rebuilds
2. HTTP serves the manual, injecting a script that triggers reload on changes
3. opens the manual in the default browser
2023-08-14 05:36:45 +03:00
## Syntax
2023-07-25 18:51:38 +03:00
As per [RFC 0072 ](https://github.com/NixOS/rfcs/pull/72 ), all new documentation content should be written in [CommonMark ](https://commonmark.org/ ) Markdown dialect.
Additional syntax extensions are available, all of which can be used in NixOS option documentation. The following extensions are currently used:
2023-08-14 05:36:45 +03:00
#### Tables
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
Tables, using the [GitHub-flavored Markdown syntax ](https://github.github.com/gfm/#tables-extension- ).
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
#### Anchors
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
Explicitly defined **anchors** on headings, to allow linking to sections. These should be always used, to ensure the anchors can be linked even when the heading text changes, and to prevent conflicts between [automatically assigned identifiers ](https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/auto_identifiers.md ).
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
It uses the widely compatible [header attributes ](https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/attributes.md ) syntax:
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
```markdown
## Syntax {#sec-contributing-markup}
```
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
> **Note**
> NixOS option documentation does not support headings in general.
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
#### Inline Anchors
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
Allow linking arbitrary place in the text (e.g. individual list items, sentences…).
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
They are defined using a hybrid of the link syntax with the attributes syntax known from headings, called [bracketed spans ](https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/bracketed_spans.md ):
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
```markdown
- []{#ssec-gnome-hooks-glib} `glib` setup hook will populate `GSETTINGS_SCHEMAS_PATH` and then `wrapGAppsHook` will prepend it to `XDG_DATA_DIRS` .
```
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
#### Automatic links
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
If you **omit a link text** for a link pointing to a section, the text will be substituted automatically. For example `[](#chap-contributing)` .
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
This syntax is taken from [MyST ](https://myst-parser.readthedocs.io/en/latest/using/syntax.html#targets-and-cross-referencing ).
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
#### Roles
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
If you want to link to a man page, you can use `` {manpage}`nix.conf(5)` ``. The references will turn into links when a mapping exists in [`doc/manpage-urls.json` ](./manpage-urls.json ).
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
A few markups for other kinds of literals are also available:
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
- `` {command}`rm -rfi` ``
- `` {env}`XDG_DATA_DIRS` ``
- `` {file}`/etc/passwd` ``
- `` {option}`networking.useDHCP` ``
- `` {var}`/etc/passwd` ``
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
These literal kinds are used mostly in NixOS option documentation.
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
This syntax is taken from [MyST ](https://myst-parser.readthedocs.io/en/latest/syntax/syntax.html#roles-an-in-line-extension-point ). Though, the feature originates from [reStructuredText ](https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-manpage ) with slightly different syntax.
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
#### Admonitions
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
Set off from the text to bring attention to something.
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
It uses pandoc’ s [fenced `div`s syntax ](https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/fenced_divs.md ):
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
```markdown
::: {.warning}
This is a warning
:::
```
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
The following are supported:
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
- [`caution` ](https://tdg.docbook.org/tdg/5.0/caution.html )
- [`important` ](https://tdg.docbook.org/tdg/5.0/important.html )
- [`note` ](https://tdg.docbook.org/tdg/5.0/note.html )
- [`tip` ](https://tdg.docbook.org/tdg/5.0/tip.html )
- [`warning` ](https://tdg.docbook.org/tdg/5.0/warning.html )
2023-07-25 18:51:38 +03:00
2023-08-14 05:36:45 +03:00
#### [Definition lists](https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/definition_lists.md)
For defining a group of terms:
```markdown
pear
: green or yellow bulbous fruit
watermelon
: green fruit with red flesh
```