[ 
https://issues.apache.org/jira/browse/SOLR-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485458#comment-17485458
 ] 

Houston Putman commented on SOLR-15556:
---------------------------------------

Ok good to know. Will continue on leaving that be :) 
 
{quote} * Have a better workflow for local development & release building. 
There should be no need to manually edit the playbook in order to test things 
out{quote}
This now works. There is a {{playbook.template.yaml}} that generates a 
{{build/playbooks/local-playbook.yml}} and a 
{{{}build/playbooks/official-playbook.yml{}}}.

By default the local settings are used, but you can provide {{gradle antora 
-Prefguide.local=false}} to build the official site (this is what the jenkins 
job does now).

Also of note, the site build now ends up in {{build/site/}} instead of 
{{{}build/{}}}. This also helps with regards to outputs for other gradle tasks.

For now I am not building in the functionality to test with a local UI bundle, 
but I will get to that eventually. I think my next task will be the solr 
javadocs links in the local build
 

> 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

Reply via email to