[
https://issues.apache.org/jira/browse/SOLR-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486142#comment-17486142
]
Houston Putman commented on SOLR-15556:
---------------------------------------
Ok we now have link checking built in. Will spend tomorrow looking at the
caching and inputs/outputs of tasks to make it so that we don't have to rebuild
the site every time.
Also, I have removed the antora plugin as it really doesn't buy us anything.
Instead we are relying on the node plugin (which the antora plugin was a very
thin wrapper over) and doing the work ourselves. This way we control how things
are done, and we can put all of the node stuff under
{{{}solr-root-dir/.gradle/node{}}}, meaning that there doesn't have to be *any*
node files under solr-ref-guide. Big win.
[~ctargett] is there any reason to keep the old jekyll build stuff in the
gradle file anymore? Can I cut it out now that we are almost at feature parity?
I see that there are some old pages that haven't been taken out of the old
jekyll src folder. I'll leave those alone, just removing the jekyll build from
build.gradle.
> Ref Guide Redesign Phase 3: Replace Jekyll
> ------------------------------------------
>
> Key: SOLR-15556
> URL: https://issues.apache.org/jira/browse/SOLR-15556
> Project: Solr
> Issue Type: Improvement
> Components: documentation
> Reporter: Cassandra Targett
> Assignee: Cassandra Targett
> Priority: Blocker
> Fix For: 9.0
>
>
> The final step of my grand vision for redesigning the Ref Guide is to look at
> replacing Jekyll with a different static site generator.
> The primary reason why is because Jekyll is designed for blog posts, not for
> sites with hundreds of static pages like ours. Back in 2017 when I chose it,
> it was relatively straightforward to implement, a lot of information was
> available in Jekyll docs and the internet in general to customize it, and it
> was one of the few that supported Asciidoc format.
> However now there are a lot more options, including some which are
> specifically designed for large multi-version documentation sites like the
> Ref Guide.
> Included with this will be reorganizing the on-disk organization of the ref
> guide files themselves.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
