I know Drupal well. It is very well suited to traditional CMS web projects, especially if there are a number of different parties supplying content in different areas of a website with workflows and approvals etc.
In this case though this is not the way to go. Way too complex, not as easily scalable as static content delivery, considerable amounts of setup and design time needed to make it work for this organization. Crucial here is that it is not easily possible to integrate all the features of a good revision control system, such as revision history, easy roll-back, transparency and reproducibility.
With static content served by one of the long-time trusted webservers, Jekyll and a revision control system such as git there will be a very simple, stable, transparent and portable environment which will stand a good chance of being easy to support even if in two or three years time a whole new team will be tasked with supporting it.
+1 for static content provided by Jekyll or similar
Am 10.01.2014 um 20:01 schrieb Olssy olssy1@gmail.com:
Jekyll seems very cool but are we sure editors and content creators prefer learning markdown than having a WYSIWYG editor in a web page? Is anyone who will be modifying the site in the future available to let us know what they prefer? Also, does Jekyll support users, roles and permissions or is this dealt with by file permissions? Will the site need more advanced features in the future that Jekyll doesn't provide such as shopping carts and forums?
I have never used Jekyll so I don't know the answers to these questions but I think they need to be asked before a final decision is made.
Here are some reasons I thought Drupal would have been a good choice: Static generation is already provided through at least 2 modules and can be implemented very quickly through the hooks that are provided out of the box. Many workflow modules exist to do things like e-mail translators when a certain piece of content is modified and needs updating. Supports users, roles, permissions, blogs, forums, localization, shopping carts, dynamic rss feeds, etc. Huge community of developers.
On Fri, Jan 10, 2014 at 1:15 PM, Gvido Glazers gvido.glazers@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@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@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@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@gmail.com wrote:
On Fri, Jan 10, 2014 at 10:10 AM, Sean Rafferty seanmrafferty@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
Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team