On Friday, May 19, 2023 at 11:24:09 AM UTC-6 Gavin wrote:
Having been around for a number of the GSOC projects, and a number of the migration projects. I'm very worried about half finished state that nobody finishes. And honestly spent a lot of time cleaning up content on jenkins.io (some were .html, some were .md, some were .txt) So to me, jenkins.io shouldn't be cut over to the new system, until the new system is fully populated. As basil mentioned, antoria is really good at what it does, and shouldn't be used for other things. The web components was effort to make uniform theming across all sites, instead of trying to merge everything into one site that tries to do a dozen different things. So my suggestion based on me trying to convert jenkins.io to gatsby a while ago and realizing its just too big 1) docs.jenkins.io (versioned, antora) I really like the idea of a new top level URL, docs.jenkins.io, for the versioned documentation and I really like the idea that it as the first goal of the project. The new top level URL can leave the existing content undisturbed until docs.jenkins.io is ready to receive some redirects. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a1193a15-9fc1-4ba0-841b-d8bc088067ben%40googlegroups.com.
