I'd be +1 on Jekyll. We can simply check in Jekyll-generated content to the site SVN as HTML/CSS/JS.
Andrus > On May 21, 2017, at 4:06 PM, Michael Gentry <[email protected]> wrote: > > On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <[email protected]> > wrote: > >> I am asking, as ObjectStyle was going to donate the time of our designer >> in the nearest future to modernize Cayenne site. So I wanted to understand >> what are the minimal branding requirements. >> > > If we are going to modernize the site, are we going to stick with Apache > CMS (is that a requirement?) or perhaps go with a more popular and actively > developed static site generator, such as Jekyll [1]? Two things I noticed > when running ASF CMS locally compared to Jekyll: > > 1. I kept having to edit the produced HTML to localize the file: CSS > references since /style.css won't work correctly. Jekyll handles this > correct. Of course, maybe ASF CMS can support this and I don't know how to > change it. > 2. Jekyll has a server option that will monitor changes as you are editing > and smartly regenerate your site, which is faster. > > > [1] https://jekyllrb.com/ -- Also the static site generator used by GitHub > Pages.
