[
https://issues.apache.org/jira/browse/SOLR-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489158#comment-17489158
]
Houston Putman commented on SOLR-15556:
---------------------------------------
No worries, completely understand.
I've removed all the old build files, keeping the {{src/old-pages}} around
until someone wants to explicitly delete them. They are not currently being
used for anything. But I don't particularly want to be the person deleting them.
I've gone and updated the {{dev-docs/ref-guide}} pages to at least give
somewhat of a start. The {{asciidoc-syntax}} page should be good to go. We
still need more information on {{{}antora.adoc{}}}, especially around the ui
stuff, but at least it's a start. I've completely removed the
{{publishing.adoc}} until we decide how that's going to go down (also if it's a
jenkins job, then the page won't need to be very large at all).
As for the landing page, I think I will use temporary existing pages for now
until you can get to it [~ctargett] . That way we can go ahead and merge this
without breaking pre-commit, if you don't get to it by the EOW. If this gets
committed with the temporary links, we can always fix it up after the merge and
backport to 9_0.
I plan on committing this by the EOW so that we don't need to continually keep
this up to date, and so that developers can start using the new docs before the
release is made. If we need to fix things still, that's not a big deal. This is
a huge win in the first place :)
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
