You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devicemap.apache.org by Radu Cotescu <ra...@apache.org> on 2014/12/22 22:18:33 UTC
website prototype update
Hello,
I've pushed the updated website prototype at [0]. The are two README files
that provide instructions on how to run the setup.
If everything looks good to you we should probably ask INFRA to set up
svnpubsub for us.
Regards,
Radu
[0] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/
Re: website prototype update
Posted by Werner Keil <we...@gmail.com>.
So like several others Tamaya and DeltaSpike use a combination of Bootstrap
and Markdown for their sites.
Not sure, if and which scripting tool was used, but ultimately it matters
less.
This is the source for the Agorava Markdown site:
https://github.com/agorava/agorava.github.io
I never personally ran the "awestruct" command, but most sites there are
just plain HTML with some Bootstrap JS and CSS.
Werner
On Fri, Dec 26, 2014 at 11:56 PM, Werner Keil <we...@gmail.com> wrote:
> Radu/all,
>
> From the look (can ask Anatole and the others in the Tamaya mailing list)
> DeltaSpike and inspired from there incubating Tamaya also seem to use it.
>
> Regards,
> Werner
>
> On Fri, Dec 26, 2014 at 11:12 PM, Radu Cotescu <ra...@apache.org> wrote:
>
>> Hi Reza,
>>
>> Yes, Jekyll just translates Markdown and templates into static HTML files.
>> It's the same engine that GitHub uses for their pages feature and if I'm
>> not mistaken it's what Cordova and CouchDB use as well for their websites
>> (or a flavour of Jekyll, anyways [3]).
>>
>> Regards,
>> Radu
>>
>> [3] - https://svn.apache.org/repos/asf/cordova/site/README.md
>> On 27 Dec 2014 00:00, "Reza Naghibi" <re...@yahoo.com.invalid>
>> wrote:
>>
>> > 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 <we...@gmail.com>
>> > To: dev@devicemap.apache.org; Reza Naghibi <re...@yahoo.com>
>> > 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
>> > <re...@yahoo.com.invalid> 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 <ra...@apache.org>
>> > To: devicemap-dev <de...@devicemap.apache.org>; Reza Naghibi <
>> > reza.naghibi@yahoo.com>
>> > 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
>> > <re...@yahoo.com.invalid> wrote:
>> >
>> > Hmm... is there any way to address the ease of publishing with this CMS
>> > solution?
>> >
>> > From: Bertrand Delacretaz <bd...@apache.org>
>> > To: dev@devicemap.apache.org
>> > Sent: Wednesday, December 24, 2014 3:35 AM
>> > Subject: Re: website prototype update
>> >
>> > On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
>> >
>> >
>> > <re...@yahoo.com.invalid> 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
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
>
Re: website prototype update
Posted by Werner Keil <we...@gmail.com>.
Radu/all,
>From the look (can ask Anatole and the others in the Tamaya mailing list)
DeltaSpike and inspired from there incubating Tamaya also seem to use it.
Regards,
Werner
On Fri, Dec 26, 2014 at 11:12 PM, Radu Cotescu <ra...@apache.org> wrote:
> Hi Reza,
>
> Yes, Jekyll just translates Markdown and templates into static HTML files.
> It's the same engine that GitHub uses for their pages feature and if I'm
> not mistaken it's what Cordova and CouchDB use as well for their websites
> (or a flavour of Jekyll, anyways [3]).
>
> Regards,
> Radu
>
> [3] - https://svn.apache.org/repos/asf/cordova/site/README.md
> On 27 Dec 2014 00:00, "Reza Naghibi" <re...@yahoo.com.invalid>
> wrote:
>
> > 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 <we...@gmail.com>
> > To: dev@devicemap.apache.org; Reza Naghibi <re...@yahoo.com>
> > 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
> > <re...@yahoo.com.invalid> 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 <ra...@apache.org>
> > To: devicemap-dev <de...@devicemap.apache.org>; Reza Naghibi <
> > reza.naghibi@yahoo.com>
> > 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
> > <re...@yahoo.com.invalid> wrote:
> >
> > Hmm... is there any way to address the ease of publishing with this CMS
> > solution?
> >
> > From: Bertrand Delacretaz <bd...@apache.org>
> > To: dev@devicemap.apache.org
> > Sent: Wednesday, December 24, 2014 3:35 AM
> > Subject: Re: website prototype update
> >
> > On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
> >
> >
> > <re...@yahoo.com.invalid> 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
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
Re: website prototype update
Posted by Radu Cotescu <ra...@apache.org>.
Hi Reza,
Yes, Jekyll just translates Markdown and templates into static HTML files.
It's the same engine that GitHub uses for their pages feature and if I'm
not mistaken it's what Cordova and CouchDB use as well for their websites
(or a flavour of Jekyll, anyways [3]).
Regards,
Radu
[3] - https://svn.apache.org/repos/asf/cordova/site/README.md
On 27 Dec 2014 00:00, "Reza Naghibi" <re...@yahoo.com.invalid> wrote:
> 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 <we...@gmail.com>
> To: dev@devicemap.apache.org; Reza Naghibi <re...@yahoo.com>
> 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
> <re...@yahoo.com.invalid> 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 <ra...@apache.org>
> To: devicemap-dev <de...@devicemap.apache.org>; Reza Naghibi <
> reza.naghibi@yahoo.com>
> 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
> <re...@yahoo.com.invalid> wrote:
>
> Hmm... is there any way to address the ease of publishing with this CMS
> solution?
>
> From: Bertrand Delacretaz <bd...@apache.org>
> To: dev@devicemap.apache.org
> Sent: Wednesday, December 24, 2014 3:35 AM
> Subject: Re: website prototype update
>
> On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
>
>
> <re...@yahoo.com.invalid> 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
>
>
>
>
>
>
>
>
>
>
>
Re: website prototype update
Posted by Reza Naghibi <re...@yahoo.com.INVALID>.
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 <we...@gmail.com>
To: dev@devicemap.apache.org; Reza Naghibi <re...@yahoo.com>
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 <re...@yahoo.com.invalid> 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 <ra...@apache.org>
To: devicemap-dev <de...@devicemap.apache.org>; Reza Naghibi <re...@yahoo.com>
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 <re...@yahoo.com.invalid> wrote:
Hmm... is there any way to address the ease of publishing with this CMS solution?
From: Bertrand Delacretaz <bd...@apache.org>
To: dev@devicemap.apache.org
Sent: Wednesday, December 24, 2014 3:35 AM
Subject: Re: website prototype update
On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
<re...@yahoo.com.invalid> 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
Re: website prototype update
Posted by Werner Keil <we...@gmail.com>.
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 <
reza.naghibi@yahoo.com.invalid> 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 <ra...@apache.org>
> To: devicemap-dev <de...@devicemap.apache.org>; Reza Naghibi <
> reza.naghibi@yahoo.com>
> 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
> <re...@yahoo.com.invalid> wrote:
>
> Hmm... is there any way to address the ease of publishing with this CMS
> solution?
>
> From: Bertrand Delacretaz <bd...@apache.org>
> To: dev@devicemap.apache.org
> Sent: Wednesday, December 24, 2014 3:35 AM
> Subject: Re: website prototype update
>
> On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
>
>
> <re...@yahoo.com.invalid> 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
>
>
>
>
>
>
>
>
Re: website prototype update
Posted by Radu Cotescu <ra...@apache.org>.
Hi,
The design on b.a.o is horrible. :( Leaving that aside I'd like to have all
our info organised on the same website. BTW, the b.a.o doesn't provide any
SEO AFAICS (check view-source:
https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0).
While I agree that editing on c.a.o is simpler, why do you think that the
Jekyll prototype comes with high costs? What are the steps in the proposed
publishing scenario that you would deem as too difficult for a bunch of
developers?
Thanks,
Radu
On Mon, Dec 29, 2014 at 8:37 PM, Bertrand Delacretaz <bdelacretaz@apache.org
> wrote:
> Have you considered using https://blogs.apache.org/ for the
> blogs/news/SEO side of things that your prototype seems to cover? We
> can get a blog just by asking, and we could keep the main site for
> more static information (and still graft your CSS on it).
>
> I agree that having a single website that does it all is nice, but as
> I said the cost in terms of lost ease of maintenance is high, and that
> gets worse as project members come and go as is often the case in our
> projects.
>
Re: website prototype update
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Radu,
On Mon, Dec 29, 2014 at 7:29 PM, Radu Cotescu <ra...@apache.org> wrote:
> ...The CSS only makes the site looks nicer, but that's about it;...
Ok, thanks for the clarifications!
Have you considered using https://blogs.apache.org/ for the
blogs/news/SEO side of things that your prototype seems to cover? We
can get a blog just by asking, and we could keep the main site for
more static information (and still graft your CSS on it).
I agree that having a single website that does it all is nice, but as
I said the cost in terms of lost ease of maintenance is high, and that
gets worse as project members come and go as is often the case in our
projects.
-Bertrand
Re: website prototype update
Posted by Radu Cotescu <ra...@apache.org>.
Hi Bertrand,
The CSS only makes the site looks nicer, but that's about it; changing the
CSS shouldn't take more than one hour with the current setup.
Things we'll not have if running the current Perl server-side templates,
without extending them:
- SEO meta tags handling based on description and keywords defined with
YAML front-matter in the posts' markdown files [3];
- the ability to conditionally display the last n news posts on the
first page, with a post excerpt (no need to display the full articles on
the homepage) [4];
- the ability to define a text-based data store like we have in the
prototype for our members [5] (this is also used for nicely adding more
context to the author of a news blog post [6][7], or for displaying the
information on the Team page [8]); we could also use this mechanism for
automatically generating download links for our releases;
- a simple way to generate RSS feeds for our News section [9].
I guess there are other features as well, but the above are the more
important ones.
Cheers,
Radu
[3] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/_includes/head.html
[4] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/index.md
(starts at {% if site.categories.news %})
[5] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/_data/members/
[6] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/_layouts/news.html
[7] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/_posts/news/2014-10-15-device-data-1.0.1-release.md
[8] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/team/index.md
[9] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/feed.xml
On Mon, Dec 29, 2014 at 8:08 PM, Bertrand Delacretaz <bdelacretaz@apache.org
> wrote:
> Hi Radu,
>
> On Mon, Dec 29, 2014 at 6:50 PM, Radu Cotescu <ra...@apache.org> wrote:
> > ...And to address one of your other concerns about the ease of use of
> cms.a.o:
> > can somebody from our committers write Perl templates to extend the
> current
> > site with the publishing features of the Jekyll prototype?...
>
> Asking from another angle, what do we lose compared to your setup if
> we just take the (much nicer) CSS from your prototype and graft it on
> the current http://devicemap.apache.org/ website?
>
> I suppose that should be reasonably easy to do, without requiring big
> changes to the CMS's Perl code.
>
> -Bertrand
>
Re: website prototype update
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Radu,
On Mon, Dec 29, 2014 at 6:50 PM, Radu Cotescu <ra...@apache.org> wrote:
> ...And to address one of your other concerns about the ease of use of cms.a.o:
> can somebody from our committers write Perl templates to extend the current
> site with the publishing features of the Jekyll prototype?...
Asking from another angle, what do we lose compared to your setup if
we just take the (much nicer) CSS from your prototype and graft it on
the current http://devicemap.apache.org/ website?
I suppose that should be reasonably easy to do, without requiring big
changes to the CMS's Perl code.
-Bertrand
Re: website prototype update
Posted by Radu Cotescu <ra...@apache.org>.
Hi Reza,
Why would you want to run a VM into a VM (the Vagrant box on top of a micro
VM) and not a VM hosted by VirtualBox directly on top of your OS running on
metal?
And to address one of your other concerns about the ease of use of cms.a.o:
can somebody from our committers write Perl templates to extend the current
site with the publishing features of the Jekyll prototype?
I don't want to impose Jekyll if there's no need for it, but having tried
to write some Perl templates for our site turned cumbersome with all of
Perl's syntactic features. Furthermore, developing templates requires to
set up the ASF's CMS Perl infrastructure on your box in order to test them
locally. I know that there's a staging feature but that will easily turn to
be quite slow when you want to see the impact of a tiny change.
I would like for us to reach an agreement soon so that we can move forward
with the site update, one way or another.
Cheers,
Radu
On Fri, Dec 26, 2014 at 6:21 PM, Reza Naghibi <
reza.naghibi@yahoo.com.invalid> 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.
Re: website prototype update
Posted by Reza Naghibi <re...@yahoo.com.INVALID>.
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 <ra...@apache.org>
To: devicemap-dev <de...@devicemap.apache.org>; Reza Naghibi <re...@yahoo.com>
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 <re...@yahoo.com.invalid> wrote:
Hmm... is there any way to address the ease of publishing with this CMS solution?
From: Bertrand Delacretaz <bd...@apache.org>
To: dev@devicemap.apache.org
Sent: Wednesday, December 24, 2014 3:35 AM
Subject: Re: website prototype update
On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
<re...@yahoo.com.invalid> 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
Re: website prototype update
Posted by Radu Cotescu <ra...@apache.org>.
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 changes
4. 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 <
reza.naghibi@yahoo.com.invalid> wrote:
> Hmm... is there any way to address the ease of publishing with this CMS
> solution?
>
> From: Bertrand Delacretaz <bd...@apache.org>
> To: dev@devicemap.apache.org
> Sent: Wednesday, December 24, 2014 3:35 AM
> Subject: Re: website prototype update
>
> On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
>
>
> <re...@yahoo.com.invalid> 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
>
>
>
>
Re: website prototype update
Posted by Reza Naghibi <re...@yahoo.com.INVALID>.
Hmm... is there any way to address the ease of publishing with this CMS solution?
From: Bertrand Delacretaz <bd...@apache.org>
To: dev@devicemap.apache.org
Sent: Wednesday, December 24, 2014 3:35 AM
Subject: Re: website prototype update
On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
<re...@yahoo.com.invalid> 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
Re: website prototype update
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Dec 24, 2014 at 2:15 AM, Reza Naghibi
<re...@yahoo.com.invalid> 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
Re: website prototype update
Posted by Reza Naghibi <re...@yahoo.com.INVALID>.
Radu,
So with this setup, do I just commit changes to SVN to have them show up on the website? 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???
From: Radu Cotescu <ra...@apache.org>
To: devicemap-dev <de...@devicemap.apache.org>
Sent: Monday, December 22, 2014 4:18 PM
Subject: website prototype update
Hello,
I've pushed the updated website prototype at [0]. The are two README files
that provide instructions on how to run the setup.
If everything looks good to you we should probably ask INFRA to set up
svnpubsub for us.
Regards,
Radu
[0] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/
Re: website prototype update
Posted by Reza Naghibi <re...@yahoo.com.INVALID>.
Awesome, I will take a look at this tomorrow.
From: Radu Cotescu <ra...@apache.org>
To: devicemap-dev <de...@devicemap.apache.org>
Sent: Monday, December 22, 2014 4:18 PM
Subject: website prototype update
Hello,
I've pushed the updated website prototype at [0]. The are two README files
that provide instructions on how to run the setup.
If everything looks good to you we should probably ask INFRA to set up
svnpubsub for us.
Regards,
Radu
[0] -
http://svn.apache.org/repos/asf/devicemap/whiteboard/devicemap-site-jekyll/