Static Site Generator Community Meeting (March 12)

[Johnny Taylor]

Jon,

I have limited experience with Jekyll, as far as ease of use goes — aside from learning some fundamentals (how it handles permalinks, for example)  — it’s relatively easy to work with. Though I found the documentation lacking in places.

And it’s blog aware. I assume being “aware” means it’ll post blog posts, but won’t handle comments? You’ll have to outsource that function to services like disqus, et al (as per our previous discussions concerning this).

I’ve yet to figure out the blog functionality, never had a reason to (now I do?), but I’ve read posting a post is as simple as marking up a piece in markdown, sticking it in a folder and generating your site. And done.

And it’s really a great system to use with Github. Commit and post via Github’s service hooks. Or whatever you use to interface with Github.

Not too sure it works with Node.js, if that is a concern.

My two cents. 

Johnny

http://abledaccess.com
http://abledaccess.com/twitter

... and the solution is inclusion





On Mar 10, 2014, at 10:16 AM, Jonathan Hung <jhung at ocadu.ca> wrote:

> Hi everyone,
> 
> It would be good if a static site generator be able to handle the following use cases: project information site, blog / project news, and documentation.
> 
> More specifically, the site generator should be able to handle:
> - complex site navigation like in the case of documentation
> - adding new content and have the structure and navigation update itself without much work (i.e. easily add a piece of news or a new blog post)
> 
> 
> Also, whatever tool we choose, we should be mindful of who will use it - the people tasked with modifying or adding content may not use these tools enough to be experts. I think we should aim for a solution where someone can pick up a set of instructions, and be able to accomplish their work without much difficulty.
> 
> To summarize:
> 
> Criteria: Easy enough for step-by-step instructions.
> Reason: Non-experts may be asked to add content.
> 
> Criteria: Be able to handle complex site navigation.
> Reason: We would like to be able to use it for documentation.
> 
> Criteria: Be able to handle news or blog style content easily.
> Reason: Project sites are updated periodically with news content.
> 
> I look forward to hearing other criteria we should consider.
> 
> - Jon.
> 
> - Jon.
> 
> 
> 
> On Thu, Mar 6, 2014 at 8:56 AM, Justin Obara <obara.justin at gmail.com> wrote:
> Recently we've been exploring the idea of moving away from larger, more complex, content management systems for the Fluid Project site and potentially other websites hosted by the IDRC. For our sites that do not require a back end server, this should both simplify the creation process and minimize on the amount of infrastructure we need to maintain it. 
> 
> For the March 12 (2:30 pm ET) community meeting we'll be discussing the criteria for selecting a static site generator. The goal of the meeting will be to come up with a set of criteria that we will use to evaluate the many static site generators against, along with concrete reasons for why those criteria are important. If you are interested and able to help out with the decision making process, from putting forward selection criteria to helping research and test possible solutions, please make sure to join the meeting. 
> 
> Community meetings are held locally at the IDRC in the collaboration room, and we are able to accommodate remote participants via Skype. If you are unable to join the meeting in person or remotely, but still would like to contribute, please feel free to reply to this thread.
> 
> If you would like to make suggestions on criteria for selecting a static site generator, please ensure you raise them in the following format 
> 
> Criteria
> Reason
> 
> 
> 
> Thanks
> Justin
> 
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
> 
> 
> 
> -- 
> JONATHAN HUNG
> 
> INCLUSIVE DESIGNER, IDRC
>  
> T: 416 977 6000 x3951
> F: 416 977 9844
> E: jhung at ocadu.ca
>  
> OCAD UNIVERSITY
> Inclusive Design Research Centre
> 205 Richmond Street W, Toronto, ON, M5V 1V3
>  
> www.ocadu.ca
> www.idrc.ocad.ca
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20140310/561253e3/attachment.html>