spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake Farrell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-1355) Switch website to the Apache CMS
Date Mon, 31 Mar 2014 18:52:15 GMT

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

Jake Farrell commented on SPARK-1355:
-------------------------------------

I've been down this road as well, Thrift started with jekyll for website generation and we
spent more time making it not act like a blog and more like a website. We eventually switched
to nanoc and had a version in testing with middleman, both of these where much easier and
flexible than jekyll. After some back and forth with [~joes] and some necessary additions
to meet our use case we switched to the Apache CMS. 

> Switch website to the Apache CMS
> --------------------------------
>
>                 Key: SPARK-1355
>                 URL: https://issues.apache.org/jira/browse/SPARK-1355
>             Project: Spark
>          Issue Type: Improvement
>          Components: Project Infra
>            Reporter: Joe Schaefer
>
> Jekyll is ancient history useful for small blogger sites and little else.  Why not upgrade
to the Apache CMS?  It supports the same on-disk format for .md files and interfaces with
pygments for code highlighting.  Thrift recently switched from nanoc to the CMS and loves
it!



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message