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

Mike Drob commented on SOLR-15556:
----------------------------------

The RAT check fails too.

I looked into it a little bit, it's because Antora uses Node, which looks like 
it uses the gradle-node-plugin and installs stuff to 
{{${project.projectDir}/.gradle}} when node/npm/yarn binaries are not available 
on the path. It also installs some stuff to node_modules, but I can't figure 
out which task controls that yet.

ref: 
https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/usage.md#configuring-the-plugin

We could move that to somewhere else, like under {{build/}} but then it would 
have to re-download every time you clean? I wish it could download to 
{{$HOME/.gradle/caches}} instead.

I think we already specified .gradle in our .gitignore, but 
validate-source-patterns and apache-rat would need to be separately configured 
to ignore all of that. We'd also want to figure out some quality of life bits 
for folks that need to switch between branches? Maybe it's ok as long as we get 
all the changes to 9.0 branch as well.



> 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