This README replaces the setup How-To orginally provided by Jekyll Now when it was forked.
This github pages version of the blog is a temporary measure until a final platform for the group blog is settled upon. At the time of writing we expect that to be one integrated with the website.
For the timebeing, Jekyll and github pages lets us publish blog posts quickly and provides an archive of content which can be migrated when appropriate.
In character, this should be a blog in the literal sense of web-log. It's more like internal tool than a public-facing channel (though of course it will be publicly accessible and should reflect that).
More substantive material from or about code pod (tutorials, essays, promotion) is probably better suited to the code pod Medium publication.
...is a well-known method for publishing static websites, especially blogs. It has a lot of flexibility and there's no need to recap those features here. Check out the Jekyll site for more information.
For Code Pod purposes, using Jekyll will reinforce baseline webdev capabilities like using github to collaborate, writing in markdown, etc.
Changing the blog's styling or functionality is relatively straightforward and ought to provide some level of challenge for an advanced beginner while being very achievable.
There is an intention that any code pod members who wish to contribute to the blog can do so.
Publishing posts is as simple as pushing a correctly formatted .md file to the repo's _posts directory.
This guide will no doubt be updated with more specific guidance on content in due course. For now, the expectation is the blog is code pod's 'conversation with itself'. It was created with the intention that the group's activities be recorded in a semi-formal fashion so that members and potential members can see what code pod is about.
eg
It's open-ended, so there's no formal classification system - common sense will hopefully be adequate.
END