For reference here is the INFRA ticket [1] for this migration task. - Ray
[1] https://issues.apache.org/jira/browse/INFRA-20633 On Tue, Aug 4, 2020 at 12:19 PM Raymond Auge <[email protected]> wrote: > David, That would be great! > > Let's see where consensus takes us. > > So far we have antora as a candidate. Does anyone else have a strong > desire to take some other solution? > > - Ray > > On Tue, Aug 4, 2020 at 12:09 PM David Jencks <[email protected]> > wrote: > >> The Camel website is mostly built with Antora (I don’t understand their >> reluctance to use it for everything). https://camel.apache.org/ < >> https://camel.apache.org/> >> >> I might be able to help with a migration to Antora. >> >> David Jencks >> >> > On Aug 4, 2020, at 8:45 AM, Romain Manni-Bucau <[email protected]> >> wrote: >> > >> > https://docs.antora.org/antora/2.3/ >> > >> > Long story short you write the doc in asciidoctor (which also means you >> can >> > bulk import html in the transition period or markdown since asciidoctor >> > supports most of markdown), then you create a descriptor file list the >> > source repos you want, then it will render all the sites properly. >> > All that generates a static website you just upload with svnpubsub (or >> git >> > flavor) or any solution you want. >> > The product website uses that and I used it for >> > https://talend.github.io/component-runtime/ >> > <https://talend.github.io/component-runtime/main/1.1.24/index.html> >> too. >> > >> > Romain Manni-Bucau >> > @rmannibucau <https://twitter.com/rmannibucau> | Blog >> > <https://rmannibucau.metawerx.net/> | Old Blog >> > <http://rmannibucau.wordpress.com> | Github < >> https://github.com/rmannibucau> | >> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book >> > < >> https://www.packtpub.com/application-development/java-ee-8-high-performance >> > >> > >> > >> > Le mar. 4 août 2020 à 17:42, Raymond Auge <[email protected] >> .invalid> >> > a écrit : >> > >> >> On Tue, Aug 4, 2020 at 11:39 AM Romain Manni-Bucau < >> [email protected]> >> >> wrote: >> >> >> >>> Hi Ray, >> >>> >> >>> Did you have a look to antora? >> >>> It is exactly designed for this kind of thing and works quite well. >> >>> >> >> >> >> I have not. Link? :) >> >> >> >> (it is not on the Apache wiki page referenced, so if it makes for a >> good >> >> story and integrates well into the Apache infra maybe we can document >> it >> >> there as well) >> >> >> >> - Ray >> >> >> >> >> >>> >> >>> Romain Manni-Bucau >> >>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> >>> <https://rmannibucau.metawerx.net/> | Old Blog >> >>> <http://rmannibucau.wordpress.com> | Github < >> >>> https://github.com/rmannibucau> | >> >>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book >> >>> < >> >>> >> >> >> https://www.packtpub.com/application-development/java-ee-8-high-performance >> >>>> >> >>> >> >>> >> >>> Le mar. 4 août 2020 à 17:30, Raymond Auge <[email protected] >> >>> .invalid> >> >>> a écrit : >> >>> >> >>>> ugh... forgot to CC you andrew. Please read back. >> >>>> >> >>>> On Tue, Aug 4, 2020 at 11:29 AM Raymond Auge < >> [email protected] >> >>> >> >>>> wrote: >> >>>> >> >>>>> Hey Andrew, >> >>>>> >> >>>>> Aries is structured as several repos where the main repo contains >> >>> several >> >>>>> sub-projects, but several other sub-projects are broken out into >> >> their >> >>>> own >> >>>>> repos. All repos are git. >> >>>>> >> >>>>> What options do you recommend for this scenario? >> >>>>> >> >>>>> It would be great if the main repo could hold the core site and then >> >>>>> separate repos contribute their content somehow. >> >>>>> >> >>>>> Any ideas how we could do that (sequenced build triggers and >> >> scheduled >> >>>>> jobs is what I'm thinking)? >> >>>>> >> >>>>> - Ray >> >>>>> >> >>>>> On Tue, Aug 4, 2020 at 10:42 AM Raymond Auge < >> >> [email protected] >> >>>> >> >>>>> wrote: >> >>>>> >> >>>>>> >> >>>>>> >> >>>>>> On Tue, Aug 4, 2020 at 10:40 AM Raymond Auge < >> >>> [email protected]> >> >>>>>> wrote: >> >>>>>> >> >>>>>>> Hi Andrew, >> >>>>>>> >> >>>>>>> The site is indeed still using the old CMS and it would be great >> to >> >>>>>>> transition it. I can try to do this. >> >>>>>>> >> >>>>>>> I'll look through the info you've sent but if there's a specific >> >>> guide >> >>>>>>> or checklist that helps migrate to any particular solution that >> >> would >> >>>> be >> >>>>>>> helpful. >> >>>>>>> >> >>>>>>> Sincerely, >> >>>>>>> - Ray >> >>>>>>> >> >>>>>>> On Tue, Aug 4, 2020 at 9:33 AM Andrew Wetmore <[email protected] >> > >> >>>>>>> wrote: >> >>>>>>> >> >>>>>>>> Infra is assembling a Wiki page [2] >> >>>>>>>> on migrating a website from the CMS, and is looking forward to >> >>> helping >> >>>>>>>> projects with this transition. >> >>>>>>>> >> >>>>>>> >> >>>>>> .. Wiki, got it! I will start with that. I may have many questions >> >> for >> >>>>>> you along the way. ;) >> >>>>>> >> >>>>>> - Ray >> >>>>>> >> >>>>>> >> >>>>>>> >> >>>>>>>> Please let me know whether your site is still on the Apache CMS >> >> and, >> >>>> if >> >>>>>>>> so, >> >>>>>>>> who will be the project point-of-contact with Infra for the >> >>> migration. >> >>>>>>>> >> >>>>>>>> Thank you! >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> [1] https://infra.apache.org/project-site.html >> >>>>>>>> >> >>>>>>>> [2] >> >>>>>>>> >> >>>>>>>> >> >>>> >> >>> >> >> >> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> -- >> >>>>>>>> Andrew Wetmore >> >>>>>>>> Technical Writer-Editor >> >>>>>>>> Infra >> >>>>>>>> *Apache Software Foundation* >> >>>>>>>> [email protected] >> >>>>>>>> >> >>>>>>>> < >> >>>>>>>> >> >>>> >> >>> >> >> >> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail >> >>>>>>>>> >> >>>>>>>> Virus-free. >> >>>>>>>> www.avast.com >> >>>>>>>> < >> >>>>>>>> >> >>>> >> >>> >> >> >> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail >> >>>>>>>>> >> >>>>>>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >>>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> -- >> >>>>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> >>>>>>> (@rotty3000) >> >>>>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com >> > >> >>>>>>> (@Liferay) >> >>>>>>> >> >>>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> >>>>>> (@rotty3000) >> >>>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> >> >>>>>> (@Liferay) >> >>>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> >>>>> (@rotty3000) >> >>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> >> >>>>> (@Liferay) >> >>>>> >> >>>> >> >>>> >> >>>> -- >> >>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> >>>> (@rotty3000) >> >>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> >> >>>> (@Liferay) >> >>>> >> >>> >> >> >> >> >> >> -- >> >> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> >> (@rotty3000) >> >> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> >> >> (@Liferay) >> >> >> >> > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay)
