[
https://issues.apache.org/jira/browse/SOLR-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479587#comment-17479587
]
Jan Høydahl commented on SOLR-15556:
------------------------------------
[~ctargett] have you made a PR for the branch yet? It would make reviewing
easier. Wow, 739 files changed :)
[https://github.com/apache/solr/compare/main...jira/solr-15556-antora]
I created SOLR-15941 for the release-related stuff we may need for releasing
this guide.
The URL structure in nightlies is currently
[https://nightlies.apache.org/solr/draft-guides/solr-reference-guide-antora/solr/HEAD/getting-started/solr-indexing.html]
What will be the final URL on the solr website? Something like
https://solr.apache.org/guide/<release-tag>/getting-started/solr-indexing.html
? Or must he current "HEAD" be exactly the name of the branch? Preferably it
would be [https://solr.apache.org/guide/9_0/getting-started/solr-indexing.html]
The new guide is multi-version. At first we'll only have 9.0 but then we'll
build 9.0 and 9.1 during the 9.1 release, and they will automatically link to
each other in a menu. But how can we make the new guide also link to the older
online guides? We can obviously not do the opposite direction easily..
> 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]
