Java vs ruby isnt really a concern. Just concerned about having to run a full
website stack just to update the site. I think having something hosted, like
cms.apache.org would be more ideal.
Would like to be democratic about this, so if people are for it, then this is
ok to move forward with.
So if we use Jekyll, our website still runs on apache httpd? Jekyll just
publishes rendered HTML to svn and that gets put behind httpd?
From: Werner Keil <[email protected]>
To: [email protected]; Reza Naghibi <[email protected]>
Sent: Friday, December 26, 2014 4:37 PM
Subject: Re: website prototype update
I know it a bit, Jekyll also runs the Agorava site.
If you prefer something similar running Java, we use JBake (www.jbake.org) for
JSR 354 and 363 project sites.
Werner
On Fri, Dec 26, 2014 at 5:21 PM, Reza Naghibi <[email protected]>
wrote:
Is there anyway to get this solution hosted? Not sure if my little micro VM can
run a headless virtualbox. Might be able to run a ruby stack, thats just
completely new territory for me, so that may not be my best option.
From: Radu Cotescu <[email protected]>
To: devicemap-dev <[email protected]>; Reza Naghibi
<[email protected]>
Sent: Friday, December 26, 2014 8:46 AM
Subject: Re: website prototype update
Hi,
The website prototype is developed with Jekyll [0]. This has the great
advantage that, as opposed to Apache's CMS, templates are developed easily
[1][2], without having to learn a new programming language. For ASF's CMS you
have to know Perl if you need more templates (e.g. blog posts, regular pages,
adding seo info from blog posts, etc.).
The Vagrant setup is only needed if it's difficult to set up Ruby + Jekyll on
your box, allowing all DeviceMap committers to run the exact same setup without
a hassle. If you're working on a machine newer than 2008 with at least 1GB of
RAM I don't think you'll have problems running the Vagrant Ubuntu Server VM
that's currently allocated 512MB of RAM. We could probably lower that amount
anyway...
I'm not sure if I can easily integrate Jekyll into ASF's CMS infra, although
there are hints that custom solutions can be adapted. However, the current
publishing scenario isn't very difficult:
1. update the content using Markdown (you can optionally use some Liquid
templating features combined with Jekyll variables)2. run jekyll to generate
the website (basically you generate the stuff from the public folder)3. commit
your work and let svnpubsub publish the changes4. enjoy your work being live on
DMAP's website
Let me know if you need any more details. To see how easy it is to modify the
website I suggest you checkout the project and give it a go on your box.
Cheers,Radu
[0] - http://jekyllrb.com/[1] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/_layouts/[2]
-
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/_includes/
On Thu, Dec 25, 2014 at 5:04 PM, Reza Naghibi <[email protected]>
wrote:
Hmm... is there any way to address the ease of publishing with this CMS
solution?
From: Bertrand Delacretaz <[email protected]>
To: [email protected]
Sent: Wednesday, December 24, 2014 3:35 AM
Subject: Re: website prototype update
On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
<[email protected]> wrote:
> ...What do I need vagrant and virtualbox for? Honestly, I don't really have a
> setup
> where I can run virtualbox. Is all of that required to publish???...
I suppose yes, and that's the downside of not using
https://cms.apache.org/, as I tried to hint to before.
-Bertrand
