I just finished reading the manual from top to bottom. Writing such comprehensive documentation is hard work, so I just wanted to say, thank you for your attention to detail, and I'm eager for the parts that are yet to be filled in.

@malcolmsparks: unrelated to yada - but the new docs look great and I familiar with Asciidoc and wouldlike to use similar format for unrelated project - are there open source stylesheets, workflow suggestions etc.

@tbrooke: we've mostly gone with the defaults and stylesheets here: https://github.com/asciidoctor/asciidoctorj

there are lots of open-source themes and options available

it really was quite straightforward to generate the book. Here's the code I used:

served of course with a yada resource:

The :state value of the yada ctx here isn't yada, I'm injecting in using a custom interceptor

In our website we keep all our application state in a tree which can be deref'd - it's just like Om's app-state or Reagent's ratom, but contains the entire state of the observeable universe (at least as far as our server is concerned) - we deref it on every request - means that for the lifetime of the request/response, the universe is frozen and consistent.

but anyway, AsciiDoc is very easy. Here's the book.adoc file

With asciidoc, includes are built in. Cross-references are super easy too, plus tables, code snippets, etc.

It is so much more consistent and powerful than markdown, imho

much better suited to writing a pile of technical documentation

@malcolmsparks: Wow Thanks and of course the html has to be served as a resource