hdt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <sma...@apache.org>
Subject Re: Website Questions
Date Thu, 07 Feb 2013 20:32:11 GMT
Hi Adam,

This link - http://www.apache.org/dev/cms.html is very useful. If you do not get to it by
weekend, I can take a stab over the weekend and help out a bit in setting this up in svn.


On Feb 7, 2013, at 2:36 PM, Adam Berry <adamb@apache.org> wrote:

> On Thu, Feb 7, 2013 at 12:26 PM, Suresh Marru <smarru@apache.org> wrote:
>> On Jan 28, 2013, at 12:00 AM, Adam Berry <adamb@apache.org> wrote:
>>>>> * To take advantage of the CMS capabilities, the website should be in
>>>> markdown
>>>>> format and html file are generated by svnpubsub format. There is a
>>>> template [2]
>>>>> for reference. Currently I see the website is directly written in HTML.
>>>>> Any particular reason? I can help with setting up in the markdown
>> format.
>>>> No reason -- I think it was the lowest hanging fruit we could pick at
>> the
>>>> time.
>>> I actually created the site using the CMS in markdown, then ran the build
>>> on my laptop and committed the result to svn. But I've been committing
>> the
>>> markdown version of the site into the git repo, so we could probably
>> switch
>>> over pretty easily.
>> Hi Adam,
>> Given that Apache CMS is integrated with svn pubsub (and I do not know if
>> there is a git integration for pub sub), I would strongly advocate for
>> website alone to be the SVN. Setting up the build locally on every one's
>> machine will pose a high barrier of entry for others to contribute to the
>> website. And more importantly this will take off the web book market
>> editing which is how 90% of the quick changes are done to CMS. I will be
>> happy to customize the instructions I put together for Airavata [1]
>> Cheers,
>> Suresh
>> [1] - http://airavata.apache.org/development/edit-cms-website.html
> Hi Suresh,
> I completely agree with you, I only mentioned that I had it in markdown
> already to say that its easy for us to just move the files where necessary.
> Moving the content to SVN is no big deal, I'm just not sure on what needs
> to go where, and then what it takes to get it wired in.
> Any pointers you have would be greatly appreciated.
> Cheers,
> Adam

View raw message