<p dir="ltr">Hi, </p>
<p dir="ltr">I've actually done some rough gh-pages styling for the workshops I've run. It was very basic as I just didn't have time. It mimics SWC. <br>
<a href="https://github.com/apawlik/2014-11-27-elixiruk-manchester">https://github.com/apawlik/2014-11-27-elixiruk-manchester</a></p>
<p dir="ltr">I don't know if there is a way of syncing master with gh-pages in some automated way. <br>
So far having just gh-pages for SWC lessons seems to be working fine. Anyways updates on the materials are done through PRs. <br>
I do like the nice layout rather than showing people markdown in GH. However, it might be because I link the lessons to the workshop pages as most attendees often ask me if they could get the copy of the materials.</p>
<p dir="ltr">So I'd be keen to keep gh-pages only </p>
<p dir="ltr">Cheers <br>
Aleksandra</p>
<p dir="ltr">Training Leader<br>
The Software Sustainability Institute<br>
w: <a href="http://www.software.ac.uk">www.software.ac.uk</a><br>
t: @aleksandrana | @SoftwareSaved</p>
<p dir="ltr">Sent from mobile, apologies for typos and weird formatting.<br>
</p>
<div class="gmail_quote">On 3 Apr 2015 18:13, "Ethan White" <<a href="mailto:ethan@weecology.org">ethan@weecology.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 03/31/2015 02:39 PM, Leah Wasser wrote:<br>
> I began to build a gh-pages branch for the python materials and found some background on syncing master and gh-pages. I then realized other repo's are not currently doing this and don't want to break the mold or do things that aren't useful to the greater mission.<br>
><br>
> Does anyone have thoughts on adding gh-page branches to the DC repos using a format similar to SWC:<br>
><br>
> <a href="http://lwasser.github.io/python-ecology/" target="_blank">http://lwasser.github.io/python-ecology/</a><br>
<br>
Thanks for raising this question Leah. The issue of how to make the<br>
lesson material easy to view and distribute has come up a few times,<br>
mainly in Steering Committee meetings I think, and it's an important one<br>
to figure out. Up until now we have basically decided to wait on making<br>
decisions about the details of the technological side of things to focus<br>
on developing content. However, with double digit workshops being run<br>
this year, and huge additional demand, this is probably something we be<br>
thinking about.<br>
<br>
As you note, Software Carpentry has grappled with this and been through<br>
a few different versions. The current version is a gh-pages only model.<br>
This is nice in that that's no branch management, which is another layer<br>
of overhead for contributors who aren't git experts. However, it results<br>
in a bunch of extra stuff in the main branch. I will say that I've found<br>
it very easy to work with the new SWC system, but if there was a behind<br>
the scenes way to sync master to gh-pages that could be really nice to.<br>
<br>
The other option is a purely external build system. Content gets<br>
developed separate from presentation, and then a regularly run external<br>
system builds web pages for all of the content periodically. But then<br>
someone has to build and maintain this.<br>
<br>
I don't personally have strong feelings about what route to go, and if<br>
you or someone else was willing to put some effort into it I'd be +1 for<br>
having you go for it.<br>
<br>
Ethan<br>
<br>
_______________________________________________<br>
dc-discuss mailing list<br>
<a href="mailto:dc-discuss@lists.idyll.org">dc-discuss@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/dc-discuss" target="_blank">http://lists.idyll.org/listinfo/dc-discuss</a><br>
</blockquote></div>