[
https://issues.apache.org/jira/browse/SOLR-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420830#comment-17420830
]
Houston Putman commented on SOLR-15556:
---------------------------------------
Thanks for updating that confluence page, it looks really complete from what I
remember making my attempt a few months ago.
If you were to start a mailing list thread, I think it would be good to first
check with the ASF Infra team that Antora support is something we can expect
going forward. (looks like it is possible, but it would be good to get best
practices from them, if they have any)
Also before making the thread we should probably have a suggested path forward
for all of the Go-No Go Decision Points, so that we have a reference point when
discussing each point.
As for those Go-No Go Decision Points:
# The having to commit thing was definitely messy for me, but according to
their documentation the author-mode will include uncommitted changes. We can
have the antora playbook use author-mode by default, then have a script
auto-update it whenever a release is made. (then change it back afterwards to
have author-mode enabled again)
# The UIBundle requirements don't really change that often, correct? If that's
the case then I have no issue using nightlies.apache.org.
> Ref Guide Redesign Phase 3: Replace Jekyll
> ------------------------------------------
>
> Key: SOLR-15556
> URL: https://issues.apache.org/jira/browse/SOLR-15556
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Cassandra Targett
> Assignee: Cassandra Targett
> Priority: Major
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
