<div>Rick Lubbers:</div><div><br></div><div>
> Why not just write a really simple PHP back-end with TinyMCE that produces plain HTML pages?</div><div><br></div><div>Jekyll (or Pelican, Middleman or $static-site-generator) are tools that do one thing and one thing well: they take markdown (or $text files) + templates and spit out a fully static website.</div><div><br></div><div>It's important to consider that it's not simply a case of spitting out plain HTML pages as thought has to be given to managing torproject.org's content structure both for launch and as the website's content grows it has to scale.</div><div><br></div><div>> Should be quite simple to implement, and with TinyMCE pretty much every moron can work with the back-end. </div><div><br></div><div>I believe writing a bespoke solution for torproject.org 3.0 introduces further complexity as opposed to using one of the proposed static site generators[1]. The proposed have mature codebases, active communities and fulfil the current technical requirements[2].</div><div><br></div><div>> Jekyll seems okay too, but still, markup language still is a kind of programming, and lots of content writers are allergic for programming.</div><div><br></div><div>Markdown is a) very easy to read and b) very easy to write[3]. I must respectfully disagree that "markup language is still a kind of programming" as in my opinion it's simply a way to structure a text document and nothing more. It's not a skip and a jump away from how one may write an email, for example.</div><div><br></div><div>Rey</div><div><br></div><div>[1] https://trac.torproject.org/projects/tor/wiki/Website#Candidates</div><div>[2] https://trac.torproject.org/projects/tor/wiki/Website#Technicalrequirements</div><div>[3] <a href="http://daringfireball.net/projects/markdown/basics">http://daringfireball.net/projects/markdown/basics</a></div>
<div></div>
<p style="color: #A0A0A8;">On Friday, 10 January 2014 at 15:18, Rick Lubbers 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">Why not just write a really simple PHP back-end with TinyMCE that produces plain HTML pages? Should be quite simple to implement, and with TinyMCE pretty much every moron can work with the back-end. <div><br>
<div><div>Jekyll seems okay too, but still, markup language still is a kind of programming, and lots of content writers are allergic for programming.</div><div><br></div></div></div></div><div><br><br>
<div>2014/1/10 Sean Rafferty <span dir="ltr"><<a href="mailto:seanmrafferty@me.com" target="_blank">seanmrafferty@me.com</a>></span><br><blockquote type="cite"><div>
<div style="word-wrap:break-word">I am currently working on a drupal project and agree that drupal is far too big and complex for the requirements laid out for tor. Something like jekyll seems much leaner and simpler.<div>
<br></div><div>As a developer, I agree that writing straight html would be nice. But there are a lot of content writers in the world that just don’t know it well enough. </div><div><div><div><br><div><div>On Jan 10, 2014, at 7:27 AM, Silviu Riley <<a href="mailto:silviu.riley@gmail.com" target="_blank">silviu.riley@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div><p dir="ltr">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. </p><p dir="ltr">We'd use git to manage the markdown files that generate the website and gerrit to approve changes. </p>
<p dir="ltr">Gerrit is in use by some Android projects. Check it out <a href="http://review.cyanogenmod.org/" target="_blank">http://review.cyanogenmod.org</a> and <a href="https://gerrit.omnirom.org/" target="_blank">https://gerrit.omnirom.org</a><br>
</p><p dir="ltr">Silviu.</p>
<div>On Jan 10, 2014 5:59 AM, "Rey Dhuny" <<a href="mailto:rey@spcshp.com" target="_blank">rey@spcshp.com</a>> wrote:<br type="attribution"><blockquote type="cite"><div>
<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 <a href="http://torproject.org/" target="_blank">torproject.org</a> 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" target="_blank">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 <a href="http://torproject.org/" target="_blank">torproject.org</a> 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/" target="_blank">http://jekyllrb.com/docs/structure/</a></font></pre><pre><font face="Helvetica">[2] <a href="http://jekyllrb.com/docs/frontmatter/" target="_blank">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"><div>
<span><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" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team</a></div></div></span>
</div></blockquote><div>
<br>
</div>
<br>________________________________________________________________________<br>
Tor Website Team coordination mailing-list<br>
<br>
To unsubscribe or change other options, please visit:<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team</a><br>
<br></div></blockquote></div>
________________________________________________________________________<br>Tor Website Team coordination mailing-list<br><br>To unsubscribe or change other options, please visit:<br><a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team</a><br>
</div></blockquote></div><br></div></div></div></div><br>________________________________________________________________________<br>
Tor Website Team coordination mailing-list<br>
<br>
To unsubscribe or change other options, please visit:<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team</a><br>
<br></div></blockquote></div><br></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>