[ 
https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jake Farrell updated MESOS-829:
-------------------------------

    Attachment: site.tar.gz

Would recommend that the following changes be made with the new site

untar and commit site.tar.gz to https://svn.apache.org/repos/asf/mesos/site/
ask infra to switch svnpubsub for the website from mesos/www/ to 
mesos/site/publish

update https://svn.apache.org/repos/asf/mesos/README

svn del  https://svn.apache.org/repos/asf/mesos/build_website.sh
svn del  https://svn.apache.org/repos/asf/mesos/website
svn del  https://svn.apache.org/repos/asf/mesos/www

I have included a README with all necessary commands in site.tar.gz to setup a 
dev environment for the website and get everything running



> Switch website CMS from Jekyll to Middleman
> -------------------------------------------
>
>                 Key: MESOS-829
>                 URL: https://issues.apache.org/jira/browse/MESOS-829
>             Project: Mesos
>          Issue Type: Improvement
>          Components: project website
>            Reporter: Dave Lester
>            Assignee: Jake Farrell
>            Priority: Critical
>         Attachments: site.tar.gz
>
>
> We currently use Jekyll as the CMS to manage the Mesos website. It does most 
> of what we need by offering templates and power to control how pages render. 
> The only issue is that when you build from source files Jekyll will wipe away 
> any hidden files in the rendered directory. This is problematic since both 
> the source and live directories are in version control (svn). Our recent 
> website revision history has been a mess, because we often end up wiping 
> out/rewriting 
> I'd like to switch the site to use Middleman to render our static site files. 
> We are using Middleman for Apache Aurora, and it doesn't face the issue of 
> wiping out hidden files. Additionally, it seems capable of all the same 
> rendering features of Markdown that we currently use. The only difference is 
> that redcarpet (the library for converting markdown to HTML) needs to use 
> ruby 3+.
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to