I have a 5 hour flight coming up next week. Should I use some of that time until my laptop battery runs out to create a new jekyll site and transfer a bit of the content over? No styling or anything, just a basic transfer of data ready for some design concept to be laid over the top.
Is that useful? Is everyone happy with jekyll as a choice? Should I just make a new personal github repo and we can move it over somewhere else later? Ari On 25/5/17 8:24am, Michael Gentry wrote: > I just published the changes. Let me know if you encounter any issues. > > As to Ari's comment of only publishing static content, the ASF CMS dynamic > editing of our site using their CMS Bookmarklet isn't all that great, so I > don't think we'd really miss/lose anything by only publishing static > content. I'd prefer to edit and preview the live/local statically > generated content, personally, and publish when we think it is correct. > > Thanks, > > mrg > > > > > On Sun, May 21, 2017 at 7:20 PM, Aristedes Maniatis <a...@maniatis.org> > wrote: > >> I'll chime in here that I love Jekyll and am currently moving my own site >> across to it. I used it also for our company intranet and (off topic) I >> highly recommend it for that purpose. >> >> If we do move to Jekyll, I'd be happy to do a bunch of the initial setup >> work. But I asked about Jekyll years ago to see if the Apache CMS supported >> it and the answer was no. So that would mean we'd need to only upload >> static content. >> >> Ari >> >> >> On 21/5/17 11:10pm, Andrus Adamchik wrote: >>> 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 <blackn...@gmail.com> >> wrote: >>>> >>>> On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik < >> and...@objectstyle.org> >>>> 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. >>> >> >> >> -- >> --------------------------> >> Aristedes Maniatis >> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >> > -- --------------------------> Aristedes Maniatis GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
