Hi Basil and Gavin, Thanks for the feedback and suggestions! We do agree with Gavin's approach that we should have the following as end goals of this GSoC project:
1) "docs.jenkins.io" (versioned, with Antora) - our first and foremost priority 2) "guides.jenkins.io" (versioned, with Antora, but less likely to update) - our next priority, or can be subsumed under "docs.jenkins.io". 3) "news.jenkins.io" a.k.a. the blog with Gatsby. hook up a headless CMS like Strapi (which we could have webhooks to update the repo). 4) Leave everything else on www.jenkins.io<http://www.jenkins.io/> or redo everything else with Gatsby. @mark.earl.wa...@gmail.com<mailto:mark.earl.wa...@gmail.com> I agree it would be a good idea for @Vandit Singh<mailto:vanditsing...@gmail.com> to strive toward a completed versioned docs section under the subdomain "docs.jenkins.io" as the minimum success metric for the GSoC project this summer. But if Vandit is feeling ambitious, as discussed internally previously we could extend his GSoC project so that more work can be completed. Also Gavin, we may need your help in setting up the new subdomains required to host the alternatively built site contents. For this I will approach you for assistance later. Best, Kris on behalf of the project mentors' team ________________________________ From: jenkinsci-dev@googlegroups.com <jenkinsci-dev@googlegroups.com> on behalf of Mark Waite <mark.earl.wa...@gmail.com> Sent: 23 May 2023 02:29 To: Jenkins Developers <jenkinsci-dev@googlegroups.com> Subject: Re: GSoC 2023 Building jenkins.io with alternative tools project feedback solicitation 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<http://jenkins.io/> (some were .html, some were .md, some were .txt) So to me, jenkins.io<http://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<http://jenkins.io/> to gatsby a while ago and realizing its just too big 1) docs.jenkins.io<http://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<mailto: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<https://groups.google.com/d/msgid/jenkinsci-dev/a1193a15-9fc1-4ba0-841b-d8bc088067ben%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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/OS3P286MB14315A761E079A0E1C03107EA1489%40OS3P286MB1431.JPNP286.PROD.OUTLOOK.COM.
