Feel free to assign that ticket to me (akm@a.o). Any volunteers to convert either the HTML files or CMS raw markup files to markdown, please get in touch.
There will be some redesign (mostly accepting theme defaults and layout limitations of markdown) necessary unless we want to invest in a perfect reproduction; we can log differences in this JIRA ticket and decide how to handle as we go. On Mon, May 20, 2019 at 12:20 PM Rich Bowen <rbo...@rcbowen.com> wrote: > > > On 5/20/19 3:08 PM, Andrew Musselman wrote: > > Assuming the goal is a straight lift and shift from CMS to pelican, I > could > > commit to starting a skeleton and setting up a workflow for other > > volunteers to convert existing content to markdown files. > > > > Not this month, but during June if that works. > > > > Works for me. Sooner than I'd get to it. > > --Rich > > > > On Mon, May 20, 2019 at 11:43 AM Rich Bowen <rbo...@rcbowen.com> wrote: > > > >> Long, long ago I opened this: > >> https://issues.apache.org/jira/browse/INFRA-15387 > >> > >> It has recently been woken up again. > >> > >> I'm looking for someone to take the reins on this, since I do not really > >> have time to do it any time before September. > >> > >> Any volunteers? > >> > >> -- > >> Rich Bowen - rbo...@rcbowen.com > >> http://rcbowen.com/ > >> @rbowen > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > >> > > > > -- > Rich Bowen - rbo...@rcbowen.com > http://rcbowen.com/ > @rbowen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
