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

[Alex Lynham]

I agree - worst case scenario, there can be a tech team that take the new .md document (or edited doc) and merge it into the git repo/branch ready for deploy. 
A

______________________Label: Superstar DestroyerWeb: http://www.hipstersunite.netI write for Prog Magazine, The Fly, This is Fake DIY and build websites. Twitter: @hipsters_unite | LinkedIn

> Date: Fri, 10 Jan 2014 15:05:46 -0600
> From: tom at tompurl.com
> To: www-team at lists.torproject.org
> Subject: Re: [Tor www-team] [Back-end][CMS]
> 
> On 01/10/2014 02:24 PM, Olssy wrote:
> > Back to your question:
> > Do we need User roles?
> >
> > If the site will ever be supporting user generated content through then
> > I think this is a requirement but if UGC is to be offloaded elsewhere
> > else and it's really just the static pages then I think the file system
> > permissions should suffice.
> 
> I'm a little confused by the definition of "user generated content". Are 
> we referring to things like blog posts and tutorials?
> 
> If so, then I think a static site generator + git still works. The 
> author would just need to create a patch (using git format-patch) and 
> then email it to this list. Someone with commit access to the www repo 
> could then apply the patch and then a post-commit hook could regenerate 
> the web site.
> 
> Granted, you would need some degree of technical savvy to do that, but 
> not much more than it would take to clone the repo in the first place.
> 
> Tom Purl
> ________________________________________________________________________
> Tor Website Team coordination mailing-list
> 
> To unsubscribe or change other options, please visit:
> https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/www-team/attachments/20140110/b13f69a5/attachment.html>