> On Jul 30, 2019, at 3:29 PM, Peter Kovacs <pe...@apache.org> wrote:
>
>
> On 31.07.19 00:18, Matthias Seidel wrote
>>> I don't understand:
>>> Why is migration necessary at all?
>> I already told you on users-de@. ASF Infra can not support the old (self
>> baked) CMS anymore.
>
> they replace it with another self baked solution... :/
No, they prefer Pelican: https://github.com/getpelican/pelican it will support
Github’s markdown and allow the preview of content within GitHub.
"the pelican setup sees the commit to master, builds the site, pushes to the
asf-site branch, which the gitpubsub sees, and pulls that change to the active
website"
There will be two major challenges.
(1) Creating our theme so that we continue to handle the NL translated elements
in the header. An example page theme template is quite similar to what the CMS
uses:
https://github.com/getpelican/pelican/blob/master/pelican/themes/notmyidea/templates/page.html
(2) How to adapt the legacy html into the new template.
I plan to help, but only after ApacheCon NA. If someone else starts the process
then I would gladly review and discuss.
Regards,
Dave
>
> With less overhead maybe.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
