Hello, Ben! Have you been able to do the content conversion and import? I'm afraid I still need to write a bit of stuff for the 5.8.0 release. Once that's done, I want to help you with the process.
Cheers! On Fri, Dec 31, 2021 at 8:43 AM Ben Weidig <b...@netzgut.net> wrote: > Hi, > > I've looked into the general problem, and it seems to be that the favored > new way for a project website is the Pelican static-site-generator with > buildbot. > At least it's the one most mentioned: > > * https://infra.apache.org/project-site.html > * > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > I've used Jekyll in the past and now Hugo for personal stuff. > Most likely, there'll be some customizations needed, but in the end, it > shouldn't matter what language is behind the SSG. > > > So the first step would be deciding which software to use and getting INFRA > involved in setting it up. > > Next, building a template to reflect the Tapestry design. > There's an ASF-template that could be used as a starting point. > > https://infra.apache.org/asf-pelican.html > > > I've exported the Confluence content as XML to look at the data, and it's a > single XML file with ~ 1.5 million lines... > Transferring it will be cumbersome, but hopefully, a converter can be used, > maybe something like > > https://gist.github.com/grugnog/2e6ee420707a8196951956cf4dbf6e91 > > > Another critical point is a stable URL structure, so Google will still have > the same content with the same URL in its index. > Hopefully, 301 rewrites can be done with htaccess files. > > I'll check out content conversion and import into a SSG in the first week > of January. > > Cheers and a happy new year! > Ben > > On Thu, Dec 30, 2021 at 5:02 PM Gavin McDonald <gmcdon...@apache.org> > wrote: > > > Although the ticket quoted below was fixed, we still need to move you > away > > from using the CMS - and that means migrating your job off of the CMS > Slave > > at ci.apache.org, it means migrating you away from using tapestry.conf > > file and it means moving you away from using built in CMS tooling like > > build_external.pl . > > > > I have created a new ticket > > https://issues.apache.org/jira/browse/INFRA-22684 > > > > Do not ignore this email or the jira ticket, the CMS WILL BE TURNED OFF > > January 31st so you must act now, so testing and enhancements can happen. > > > > Gav... > > > > > > On 2021/09/16 15:56:50 Gavin McDonald wrote: > > > Hi All, > > > > > > As you should be aware by now, the CMS is deprecated and going away. > > > You are one of the last remaining projects still using the CMS (in part > > anyway) > > > to publish your website. > > > > > > An Infra ticket (https://issues.apache.org/jira/browse/INFRA-22208) > was > > opened as > > > your site no longer publishes. We will not be 'fixing' the problem that > > currently exists > > > but rather we want to get you off of the CMS and publishing using a > > different method. > > > > > > Please liaise on the existing ticket above and we'll help get you > there. > > > > > > Thanks > > > > > > Gavin McDonald (ASF Infra) > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > > > For additional commands, e-mail: dev-h...@tapestry.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: dev-h...@tapestry.apache.org > > > > > -- Thiago
