Is the AsciiDoc source also on GitHub? Some things that I noticed:
- The FAQ sidebar navigation is great! The TOC list at the top isn't needed at all now. - In the breadcrumb trail (e.g., ASCIIDOC_POC > Cassandra > FAQ, or ASCIIDOC_POC > Cassandra Documentation > Glossary), *Cassandra* in the Cassandra pages isn't a link but Cassandra Documentation is. - Some of the code blocks are off (e.g, https://polandll.github.io/site/ASCIIDOC_POC/4.0/cassandra/cql/indexes.html#create-index-statement, https://polandll.github.io/site/ASCIIDOC_POC/4.0/cassandra/cql/mvs.html) - Pandoc clobbered the "MV select" part in https://polandll.github.io/site/ASCIIDOC_POC/4.0/cassandra/cql/mvs.html into the preceding note. I wonder if it will be worth it to try rSt -> HTML (using the current build tools) -> AsciiDoc (using Pandoc). Yours, Murukesh Mohanan On Thu, 11 Jun 2020 at 03:21, Lorina Poland <lor...@datastax.com> wrote: > Hello all! > > Based on an earlier discussion about moving the OSS C* docs to > asciidoc, to allow more flexibility in maintaining the docs, I've done > a proof of concept about what it would take to accomplish a > conversion. I converted rSt files to asciidoc files using pandoc, did > some additional editing, and use antora (antora.org) as a static site > generator to build the docs. The result is here: > > https://polandll.github.io/site/ASCIIDOC_POC/4.0/cassandra/getting_started/configuring.html#changing-the-location-of-directoriesThe > editing of the docs is NOT complete, but I completed enough to feel > confident that this process can be accomplished. Some YAML > configuration for antora was required, and I did a minimum of UI > configuration (added color banner, logo). Looking for feedback and > questions anyone may have. > > Thanks, > > Lorina Poland (DataStax tech writer) >
