[jira] [Commented] (SOLR-15556) Ref Guide Redesign Phase 3: Replace Jekyll

["Mike Drob (Jira)" <ji...@apache.org>]

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

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

I tried checking out the branch and building it via {{./gradlew antora}}

 I get the following failure consistently:

{noformat}
> Task :solr:solr-ref-guide:antora
npx: installed 62 in 2.752s
{"level":"fatal","time":1642700921428,"name":"antora","err":{"type":"Error","stack":"Error\n    at /Users/mdrob/code/solr/solr/solr-ref-guide/node_modules/@antora/ui-loader/lib/load-ui.js:95:15\n    at async Promise.all (index 0)\n    at async GeneratorContext.loadUi (/Users/mdrob/code/solr/solr/solr-ref-guide/node_modules/@antora/ui-loader/lib/load-ui.js:102:17)\n    at async Promise.all (index 1)\n    at async generateSite (/Users/mdrob/code/solr/solr/solr-ref-guide/node_modules/@antora/site-generator/lib/generate-site.js:17:5)\n    at async Command.parseAsync (/Users/mdrob/.npm/_npx/71979/lib/node_modules/@antora/cli/node_modules/commander/lib/command.js:923:5)"},"msg":"Specified UI bundle does not exist: /Users/mdrob/code/solr/solr/solr-ref-guide/ui/build/ui-bundle.zip (resolved from url: ./ui/build/ui-bundle.zip)"}
{noformat}

I'm not sure what the failure was that you were talking about [~ctargett] that fails the first time but succeeds on future attempts.

> 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-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org