I like the idea if Jekyll, though I've never used it myself. Running a git repo and gerrit will make our use of Jekyll easier.

We'd use git to manage the markdown files that generate the website and gerrit to approve changes.

Gerrit is in use by some Android projects. Check it out http://review.cyanogenmod.org and https://gerrit.omnirom.org

Silviu.

On Jan 10, 2014 5:59 AM, "Rey Dhuny" <rey@spcshp.com> wrote:
> Can anyone explain a bit how Jekyll would work in the context of the Tor website?

In terms of the Tor website it would be a case of completely replacing the current Drupal implementation with a website built on Jekyll.

In practice this would require moving all the content current found on torproject.org into markdown files.

Each markdown file would have a `layout`[1] defined in the YAML frontmatter[2] which exists on the top of the markdown file.

As a simplified example, a blog post's frontmatter may look like:

```
---
layout: post
title: "Tor Weekly News"
tags:
- weeklynews
- browserbundle
---
```
And a page's frontmatter may look like:

```
---
layout: page
title: "Documentation"
---
```
The documentation has an example of a basic directory structure: http://jekyllrb.com/docs/structure/


> Do users need to create the content on disk or through a web interface?
There is currently no implementation of a `web interface` in Jekyll (although you could argue that GitHub's web edit interface fills this need, that's not relevant to this implementation).
To create content users would create on disk. How a user gets this created content to torproject.org is an important consideration. Would they commit this to a git repo? Would they upload to trac? Etc.
Rey
[1] http://jekyllrb.com/docs/structure/
[2] http://jekyllrb.com/docs/frontmatter/

On Thursday, 9 January 2014 at 22:08, Olssy wrote:

Starting this thread to discuss the different solutions, what they offer and how many people have used them before.

I know Drupal better than other CMSs and it fits the requirements although static generation is not out of the box but supported by a module(like most things in Drupal). Content is usually created and modified through a web interface that offers either source code view or a WYSIWYG GUI but can be template based using text files on disk.

Can anyone explain a bit how Jekyll would work in the context of the Tor website? Do users need to create the content on disk or through a web interface?
________________________________________________________________________
Tor Website Team coordination mailing-list

To unsubscribe or change other options, please visit:


________________________________________________________________________
Tor Website Team coordination mailing-list

To unsubscribe or change other options, please visit:
https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team