[
https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050124#comment-16050124
]
Konrad Windszus commented on SLING-6955:
----------------------------------------
Could someone list here quickly the drawbacks of the Apache CMS
(https://www.apache.org/dev/cms.html)? Currently I am not clearly seeing what
problems we try to solve with the new website. Let me start the list here with
things I see
# Local builds are hard to achieve
# Based in SVN instead of Git
# It seems that the Apache CMS is basically no longer maintained/developed
But migrating the website again seems quite some effort, given the fact that
even the last migration is not 100% finished yet...
> Convert Sling website to JBake and gitpubsub
> --------------------------------------------
>
> Key: SLING-6955
> URL: https://issues.apache.org/jira/browse/SLING-6955
> Project: Sling
> Issue Type: Bug
> Components: Site
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> I've started experimenting with JBake to generate the Sling website. If that
> works well we might switch to that + gitpubsub to have a more flexible way to
> generate the site.
> My current experiment is at https://github.com/bdelacretaz/sling-jbake, at
> this point the site starts looking like the current one and many pages work
> well.
> Internal links will need to be converted, all *.md files need a more complete
> "front matter" section, currently I have a stub for that, and I think images
> need to move under the assets folder.
> To play with that, generate the site with the bake.sh script (setup
> shamelessly copied from https://github.com/apache/incubator-tamaya-site)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
