I meant they support building your site from source automatically via Pelican similar to how GitHub supports Jekyll sources to generate the HTML from. Since we generate the HTML manually from Maven, you can use either service as they both support static contents. It's only a difference if we were using another system for generating the site.
On Tue, 4 Aug 2020 at 10:00, Gary Gregory <garydgreg...@gmail.com> wrote: > > On Tue, Aug 4, 2020 at 10:56 AM Matt Sicker <boa...@gmail.com> wrote: > > > See also the asf-site and asf-staging branches for an Infra-supported > > site publishing system: > > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features > > > > Seems to work fairly similar to a gh-pages branch, though they offer > > Pelican instead of Jekyll. Though since Commons sites are all > > statically generated from Maven, it doesn't matter which you use as > > you can simply commit the output files to one of those special > > branches. > > > > Hi Matt, > > I was not planning on changing how we deal with component sites, just the > Commons site itself. Or am I missing something? > > Personally, I also don't want to use Jekyl/Pelican, I'd prefer to go > straight to GitHub. > > Gary > > > > > > On Tue, 4 Aug 2020 at 08:57, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > > HI Andrew, > > > > > > I think we use both CMS and Buildbot if that makes any sense [1], but > > > whatever it is, it's no longer working [2][3], so I'm happy to switch. > > > > > > I see GitHub pages as an option, so why not go with that. > > > > > > Commons its own site obviously but it also has a lot of components each > > > with their own site. Each component site does not use CMS, it is > > published > > > manually as part of a release. > > > > > > So this migration should only apply to the Commons site and not component > > > sites, right? > > > > > > Gary > > > > > > [1] https://commons.apache.org/site-publish.html > > > [2] https://ci.apache.org/builders/commons-site-staging > > > [3] https://issues.apache.org/jira/browse/INFRA-20632 > > > > > > > > > > > > > > > > > > On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore <andr...@apache.org> > > wrote: > > > > > > > Hi: > > > > > > > > I am part of the Infrastructure team, and am writing to ask whether > > your > > > > project is still using the Apache CMS for your project website. As you > > > > know, the CMS is reaching end-of-life, and we need projects to move > > their > > > > websites onto a different option within the next few weeks. > > > > > > > > There are several alternatives available, including those listed on > > this > > > > page [1] on managing project websites. Infra is assembling a Wiki page > > [2] > > > > on migrating a website from the CMS, and is looking forward to helping > > > > projects with this transition. > > > > > > > > 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* > > > > andr...@apache.org > > > > > > > > < > > > > > > 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> > > > > > > > > > > > > -- > > Matt Sicker <boa...@gmail.com> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > -- Matt Sicker <boa...@gmail.com> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
