Hi, I'm only creating repo and migrating history to be able to evaluate antora. This CMS needs repo in place to get the more of it. If not conclusive I would remove the repo. I prefer doing it under apache as I migrate history of the website repo. Consider the netbeans-antora-* just test for now. I will need to move file around to fit antora placement. And redo a bit of templating to have a fair comparison.
Speaking on the current build problem is CI (jenkins or github action are unable to start --no-daemon as gradle detect something not matching with jvm, tested on ci apache and a custom jenkins), note that Antonio say it may be scss, but me building it with no issue on cli. (Tested on ubuntu like 20 / 22). So since mid septembre the merged PR are not online. I'm not aware on lots of CMS, but I know Antora and Antonio raise the name as an example. I like it as it keep asciidoc in adoc format as we currently have, and templating is very close to gsp. (I have a simple test that give same output for website, (frontpage,standard page)) Antora cli check xref, image link on build something current build cannot issue some warning on fragment. (Hi sometime check with PR#617 but that's not in current build). I personnaly use jbake, (mavenized at office) and Jekyll for github page for university master website. But Jekyll AFAIK is "bind" kramdown. Best Regards Eric -----Message d'origine----- De : Matthias Bläsing <mblaes...@doppel-helix.eu.INVALID> Envoyé : mercredi 4 octobre 2023 21:12 À : dev@netbeans.apache.org Objet : Re: website migration to antora Hi, Am Montag, dem 02.10.2023 um 10:56 +0200 schrieb Eric Barboni: > > I'm a bit annoyed by the current gradle build and would like to > migrate to antora, means one repo for UI (css, and so one) and 1 to > more repository for the content (keeping adoc). > I don't understand why this question was asked if the result does not matter? The work is underway, so I assume, it is already decided (how?). At least the multiple already created repositories to me indicate this. Questions that might have been raised: - What is the real problem with the current build? - Which other static CMS systems were evaluated? - Why is antora better than the other systems and better than the current build? Greetings Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
