Post on Lesson Metadata

Draft of blog post on metadata and lesson templates, not ready for merge
Good catch, will fix

-- 
Gabriel A. Devenyi B.Eng. Ph.D.
Research Computing Associate
Computational Brain Anatomy Laboratory
Cerebral Imaging Center
Douglas Mental Health University Institute
McGill University
t: 514.761.6131x4781
e: gdevenyi@gmail.com

On Mon, Oct 6, 2014 at 1:47 PM, Matt Davis <notifications@github.com> wrote:

> In blog/2014/10/of-templates-and-metadata.md:
>
> > +author: Gabriel A. Devenyi
> > +title: "Of Templates and Metadata
> > +date: 2014-10-06
> > +time: "10:00:00"
> > +category: ["Tooling"]
> > +---
> > +Greg recently posted as an appendix to the [splitting the repository post](http://software-carpentry.org/blog/2014/09/splitting-the-repo.html) a straw man template for how lessons might be structured after the repo split.
> > +There a lot of good ideas there on how we can encourage good structure for lessons and help learners and instructors alike for software carpentry going forward.
> > +This post is going to directly reference and comment on the content of that post so its considered mandatory reading to understand what I'm talking about.
> > +
> > +# Templates and Metadata
> > +
> > +First, I want to look at the templates from a slightly different perspective, how we should structure these templates in order to assist in programmatically building the site and the workshops, as well as assisting in sharing.
> > +Some of these ideas have been discussed in a different context on Greg's post on [a new template for workshop websites](http://software-carpentry.org/blog/2014/10/a-new-template-for-workshop-websites.html).
> > +
> > +To assist in the production of workshop websites and to better define the relationship between, some lesson repositories should contain some metadata.
>
> "some lesson repositories"? Why not all of them?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/swcarpentry/site/pull/624/files#r18472206>.
>