[jira] [Comment Edited] (MESOS-829) Switch website CMS from Jekyll to Middleman

["Ross Allen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851071#comment-13851071 ] 

Ross Allen edited comment on MESOS-829 at 12/17/13 11:12 PM:
-------------------------------------------------------------

We could make Jekyll generate to a different directory and then move its output into the www directory. That would be two commands instead of 1-per-.svn-directory and allow Jekyll to wipe out whatever it wants in its temp build directory.

Can I send reviews for the website, or how does that work?


was (Author: ssorallen):
We could make Jekyll generate to a different directory and then move its output into the www directory. That would be two commands and allow Jekyll to wipe out whatever it wants in its temp build directory.

Can I send reviews for the website, or how does that work?

> 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: Dave Lester
>            Priority: Critical
>
> 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.4#6159)