Since Nix/NixOS/Nixpkgs manuals are on white backgroud, I'd say we use github colors for now.

Also, do not highlight, or highlight properly output messages which are using asymmetric quotation marks.

http://nslqqq.github.io/nixpkgs/sec-configuration-syntax.html#sec-configuration-file

Same page, add support for multi-line strings.

  foo = ''
    text
  '';

@domenkozar , @nbp
Ok, I have set github theme, fixed highlighting and quotes.
Cleaned up, updated preview

Added selflinks to headers as described in #4965.
Set output mode to single-html as it more user friendly(also discussed in #4965)

+1, except one-page html (that probably needs a bit more discussion).

Personally, I don't see any benefit of multi-page html and agree with @spwhitt, @wmertens and @chaoflow. But now I see that docs were previously single-paged and were splitted afterwards in 81f2749. Reasons for that are not clear for me.

Where does highlight.pack.js come from, and how is it (re)generated?

Attribute paths are not highlighted correctly - only the last element is coloured (e.g. in networking.hostName, only hostName is coloured).

@edolstra i got it from https://highlightjs.org/download/ , Custom packages section. Building it will require nodejs(http://highlightjs.readthedocs.org/en/latest/building-testing.html).

That's how I wrote the highlighter for highlight.js - we can change that for the next version if wanted. I find it nice to highlight only the last option (took the idea from vim highlighter).

See highlightjs/highlight.js#399

I updated asymmetric quotes thing, these snippets are now ignored.

What do you think about highlightjs script itself though? Wouldn't it be better to depend on nodejs and generate&minify it on the fly?

Why would we? We only need to update if Nix highlighter changes. I'd only add docs to describe how to update highlight.js

Well, i don't know, but it seems to be nice thing to do, and its in nix spirit. We use nix to build docs anyway. Now its simpler, but a bit ugly in my opinion. Also that way it will be kinda self documented.

I separated options and manual as discussed in #7607

@domenkozar @nmikhailov Can we rebase this work and get it merged?

Yeah I'm planning to do that for 16.03 (but it's low priority)

It took exactly three years, but I've merged a PR adding syntax highlighting. Thank you for providing the base on which I implemented #37901.