openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <wave4d...@comcast.net>
Subject Re: [discussion] CMS migration (was: svn migration plan)
Date Mon, 29 Jul 2019 15:56:13 GMT
BTW -

A good portion of the site is html as donated in 2011. It is extracted using additional functions
in the CMS and then wrapped in the templates.

There is about 9GB content and as the template was developed we hammered the CMS system.

We will need to revisit how we handle NL for the headers. I did the bulk of the work in Dec
2011. No real plans to help until after Apachecon.

Please keep the OpenOffice website in SVN until a Git based framework using new tools is built.
Once it is we can do a bulk move which could include html conversions.

Personally, I kind of like the JBake approach used in the Incubator ...

Regards,
Dave

Sent from my iPhone

> On Jul 29, 2019, at 7:33 AM, Raphael Bircher <rbircherapache@gmail.com> wrote:
> 
> Hi Gavin
> 
> Sounds like a load of work, Especially for the Templates. Does Pelican
> serve HTML and markdown mixed?
> 
> Regards Raphael.
> 
>> On Mon, Jul 29, 2019 at 10:48 AM Gavin McDonald <ipv6guru@gmail.com> wrote:
>> 
>> Hi all,
>> 
>>> On Mon, Jul 29, 2019 at 9:18 AM George Karalis <thorbust@gmail.com> wrote:
>>> 
>>> Hello Peter,
>>> 
>>> I have proposed some time ago the move to a static site generator — like
>> Jekyll, Hugo etc. —
>>> as I was redesigning OpenOffice’s front-page. That would greatly help
>> reduce tech diversity
>>> and maintenance as only static html files will be served.
>>> 
>>> Most static site generators work with markdown and I believe that content
>> writers won't have
>>> a problem working with markdown. We could also setup an automated build
>> pipeline that
>>> serves the generated site with every commit, i.e. every markdown or
>> template change.
>> 
>> 
>> Hi George, you have just described almost perfectly Infras replacement for
>> the CMS!
>> Using Pelican and GHFM and Buildbot, you only need to 'edit' a page in
>> Github and that
>> commit will trigger a site rebuild and automatic publish of the site. It is
>> still in testing but
>> almost ready for use. I'll post more details and a docs link when its ready
>> for wider testing.
>> 
>> Gav...
>> 
>> 
>>> 
>>> 
>>> By the way there's a fully functional redesigned front-page for anyone
>> interested, that time
>>> there was a server migration and it hadn't got much attention. The CMS
>> migration provides an
>>> opportunity to move to a whole website redesign.
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>> 
>> 
>> 
>> --
>> Gav...
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message