mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Lester (JIRA)" <>
Subject [jira] [Commented] (MESOS-829) Switch website CMS from Jekyll to Middleman
Date Mon, 20 Jan 2014 23:16:23 GMT


Dave Lester commented on MESOS-829:

Great, I added to the Rakefile to remove the md extensions from documentation links, and pushed
this change to subversion. Thanks [~jfarrell] for your huge help here.

I've create a ticket, INFRA-7216, to switch SvnPubSub. After that's completed, I can clean
up the remaining files in subversion.

> Switch website CMS from Jekyll to Middleman
> -------------------------------------------
>                 Key: MESOS-829
>                 URL:
>             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

View raw message