<div>
<div dir="ltr">> Can anyone explain a bit how Jekyll would work in the context of the Tor website?</div><div dir="ltr"><br></div><div>In terms of the Tor website it would be a case of completely replacing the current Drupal implementation with a website built on Jekyll.</div><div><br></div><div>In practice this would require moving all the content current found on torproject.org into markdown files.</div><div><br></div><div>Each markdown file would have a `layout`[1] defined in the YAML frontmatter[2] which exists on the top of the markdown file.</div><div><br></div><div>As a simplified example, a blog post's frontmatter may look like:</div><div><br></div><div>```</div><div>---</div><div><pre><font face="Helvetica">layout: post
title: "Tor Weekly News"
tags:
- weeklynews
- browserbundle</font></pre><pre><font face="Helvetica">---</font></pre><pre><font face="Helvetica">```</font></pre><pre><font face="Helvetica">And a page's frontmatter may look like:</font></pre><pre><div style="white-space: normal; "><font face="Helvetica">```</font></div><div style="white-space: normal; "><font face="Helvetica">---</font></div><div style="white-space: normal; "><pre><font face="Helvetica">layout: page
title: "Documentation"
<span style="white-space: normal; ">---</span></font></pre><pre><font face="Helvetica">```</font></pre><pre><font face="Helvetica">The documentation has an example of a basic directory structure: </font><a href="http://jekyllrb.com/docs/structure/" style="white-space: normal; ">http://jekyllrb.com/docs/structure/</a></pre></div></pre><pre><font face="Helvetica">> Do users need to create the content on disk or through a web interface?</font></pre><pre><font face="Helvetica">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).</font></pre><pre><font face="Helvetica">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.</font></pre><pre><font face="Helvetica">Rey</font></pre><pre><font face="Helvetica">[1] <a href="http://jekyllrb.com/docs/structure/">http://jekyllrb.com/docs/structure/</a></font></pre><pre><font face="Helvetica">[2] <a href="http://jekyllrb.com/docs/frontmatter/">http://jekyllrb.com/docs/frontmatter/</a></font></pre><pre><br></pre></div>
</div>
<p style="color: #A0A0A8;">On Thursday, 9 January 2014 at 22:08, Olssy wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div dir="ltr">Starting this thread to discuss the different solutions, what they offer and how many people have used them before.<div><br></div><div>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.</div>
<div><br></div><div>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?</div></div>
</div><div><div>________________________________________________________________________</div><div>Tor Website Team coordination mailing-list</div><div><br></div><div>To unsubscribe or change other options, please visit:</div><div><a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team">https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>