tazjin

btw, unrelated, but your `CONTRIBUTING.md` contains my email address :P

Interesting, I have to take a more detailed look at what this actually implies, but I have two superficial comments: 1. Please keep the `#[macro_use]` annotation, `nixdoc` should build on...

> if it makes sense to convert this library to output CommonMark instead of Docbook That's probably reasonable! Depending on the structure you're opting for it's likely much easier than...

Here are my current thoughts on the topic: #### What we have right now People have over time converged onto a relatively common structure for comments, which is what `nixdoc`...

[Here is some interesting discussion](https://internals.rust-lang.org/t/rustdoc-restructuredtext-vs-markdown/356/18) from the Rust community about reStructuredText.

> Good luck to the brave soul who wants to reimplement the nix manuals in it, though :wink: I for one want to be very clear that this issue is...

Hey! We do have a NixOS module for Nixery in TVL: https://cs.tvl.fyi/depot/-/blob/ops/modules/nixery.nix This actually runs the public nixery.dev instance. It only supports local storage at the moment, but could be...

> We just bump error tokens as trivia so they appear in the tree, but don't report them as errors. Hmm, not sure I understand the implication of this. We'd...

I'm guessing this is a duplicate of #146. It should be possible to have rnix report these as errors

This would be beneficial for those that don't want to lose the type-safety of `error-chain` but have to interface with crates using `failure`!