[Tor www-team] [Back-end][CMS]

Fri Jan 10 18:49:17 UTC 2014

Hi there,

I too think we should probably go for something like Jekyll but alternatives like Middleman should be investigated more thoroughly. After all this is a decision with some consequences. Possible criterias:

* support for mulitlinguality
* support for large sites / complex navigation
* performance
* usability sugar like graphical admin frontend, wysiwyg markdown editor wouldn’t hurt
* integration with Git (not sure if there are differences in this respect)

Oh, and, btw: I’m Thomas, currently working on another Tor project and therefor more lurking in this one then actually being able to contribute much right now, but definitely interested. My expertise is more with HTML, CSS, Javascript, interface design, “information architecture”.  I did a CSS based redesign of de.indymedia.org 10 years ago of which I’m still proud but got a little rusty with my web skills lately while I concentrated on trying to become a real computer scientist (by studying it at university, uh oh).

Cheers
Thomas

On 10 Jan 2014, at 19:21, Namanyay Goel <mail at namanyayg.com> wrote:

> While Jekyll is indeed a choice, for larger sites, it's generation time is simply too long. Development takes time on Jekyll, simply because of it's generation time. If we can offset that problem in some way, that would be great, otherwise I feel we should be looking at some other static site generator (Someone suggested Middleman? It also has internationalization!)
> 
> As for the debate about author's writing 'code', Markdown is easy to learn and use, and outputs semantic data. We really don't need a rich text editor of some sort, Markdown (Or similar languages) are good enough. 
> 
> 
> On Fri, Jan 10, 2014 at 11:45 PM, Gvido Glazers <gvido.glazers at gmail.com> wrote:
> Hello, Everyone!
> Missed the introduction thread, so I'll just start with that:
> I'm Gvido, and I'm currently based in Amsterdam.
> My official job title is front-end developer, but in reality I do full-stack development with ruby or python.
> 
> 
> Now, back on topic. 
> I'm also going to agree with the general sentiment that Jekyll is the way to go. It's stable, simple, widely used, easy to extend, and powerful.
> Markdown is really easy to learn, I don't think content creators writing about Tor would have a problem grasping it.
> 
> 
> On Fri, Jan 10, 2014 at 6:52 PM, William Papper <william at papper.me> wrote:
> Definitely a +1 for Jekyll. There's no need to reinvent the wheel. While a custom solution or plain HTML may seem appealing at first (and would be great for a personal project), Jekyll lets us move much quicker and keeps everything relatively standardized. It also makes it easier for people to collaborate, since Jekyll is widely used.
> 
> 
> On Fri, Jan 10, 2014 at 11:57 AM, Moritz Süß <moritz at moritzsuess.de> wrote:
> Markdown is _very_ simple.
> Please check out http://daringfireball.net/projects/markdown/basics and try out markdown at http://www.markdownviewer.com/.
> 
> Let’s try to use these as long as possible for getting people familiarized with Markdown. We do not want to duplicate existing documentation efforts, and keep up-front investment for tools as low as possible in this project.
> 
> I hope I am correct in my understanding that we agree on a static website generator now, and kind-off agree on Jekyll.
> 
> Best
> Moritz
> 
> Am 10.01.2014 um 17:35 schrieb Earl G <globallogins at gmail.com>:
> 
>> Ok So Jeklly
>> a user guide for people that need to learn markdown to be able to contribute to the blog.
>> 
>> and the front of the site user friendly for anybody that wants to get started.
>> 
>> back of the site and deeper for the linux nerds and specialists that want to dig deeper.
>> 
>> job done
>> 
>> 
>> 
>> On 10 January 2014 17:32, Sam E. Lawrence <selbrit at gmail.com> wrote:
>> 
>> On Fri, Jan 10, 2014 at 10:10 AM, Sean Rafferty <seanmrafferty at me.com> wrote:
>> But there are a lot of content writers in the world that just don’t know it well enough. 
>> 
>> Then they can learn. If someone wants to contribute to a solution to a problem as complex as privacy and security, then learning markdown / HTML should be a minor investment of their time. Basic HTML takes little time to learn, and will instantly boost the self-respect of anyone who wants to help Tor and other software projects. Setting a bar is worth it, IMO.
>> 
>> ________________________________________________________________________
>> Tor Website Team coordination mailing-list
>> 
>> To unsubscribe or change other options, please visit:
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
>> 
>> 
>> ________________________________________________________________________
>> Tor Website Team coordination mailing-list
>> 
>> To unsubscribe or change other options, please visit:
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
> 
> 
> ________________________________________________________________________
> Tor Website Team coordination mailing-list
> 
> To unsubscribe or change other options, please visit:
> https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
> 
> 
> 
> ________________________________________________________________________
> Tor Website Team coordination mailing-list
> 
> To unsubscribe or change other options, please visit:
> https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
> 
> 
> 
> ________________________________________________________________________
> Tor Website Team coordination mailing-list
> 
> To unsubscribe or change other options, please visit:
> https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
> 
> 
> 
> 
> -- 
> Namanyay Goel
> 
> :: Freelance Web Designer and Developer.
> :: UI Designer at MakeUseOf.
> :: Author at Symmetrycode.
> :: @namanyayg
> 
> ________________________________________________________________________
> Tor Website Team coordination mailing-list
> 
> To unsubscribe or change other options, please visit:
> https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team

thms/ao          thomas lörtsch        tl at rat.io 
                 hospitalstr. 95       tomlurge at someOtherServices
   °|´         d 22767 hamburg         +49 173 202 71 99
   ^^^

		 30c3: To Protect And Infect, Part 2
                 http://www.youtube.com/watch?v=b0w36GAyZIA