Seems like even Antora uses another SSG called middleman for their “marketing”
home page.
https://gitlab.com/antora/antora.org
If the convenience of having both content and docs all in one SSG for code
maintenance is compatible with the aesthetic/ content / taxonomy strategy need
for the site
Folks,
I applaud the choice of Antora for documentation but I’m not sure it is the
best choice for generating an appealing site.
Antora’s self professed strength is in technical documentation. Do we want to
stick to a “documentation” / utility look for the front facing site or for a
blog?
htt
Thanks for the comments, Mick.
Yes, I think you are correct in what you have to say about versioned vs
non-versioned docs for the website. It's such an obvious comment that I can
only say I must have been half-asleep when Anthony and I discussed the
topic. (Maybe he was, too!)
Since Antora is one
> About space efficiency, one of the biggest drawback of SASI was the huge
space required for index structure when using CONTAINS logic because of the
decomposition of text columns into n-grams. Will SAI suffer from the same
issue in future iterations ?
SAI does not have specific ngram support atm
As part of the work, I think all content files should be moved to
> cassandra/doc. This would give a clear separation of concerns;
> - cassandra/doc contains the material (asciidoc) that is converted to the
> website content.
> - cassandra-website hosts the live content and contains all the UI
>
