Here's the one I started that also has a
course.json, but I am completely redoing it as an assignment starter and with TOML instead of JSON (although the course.json will also be built by the
docmaker (or whatever it ends up being named). I plan on reserving the
www directory of the the course repos to contain a Phonegap-able miniapp containing the documentation built from a combination of README.md, with the structure in the TOML and then "styled" with some sort of probably React navigation button built into it. I had been playing around with a docmaker earlier but think I'm going to go with a golang version so the command line tool could be run on any supported OS without additional installations. This way students can use their tablets or phones to follow along, even mark off the GitHub Flavored Markdown check boxes for their own local reference as they work through the assignments in the course sort of like having a text book instead of having to go back and forth with windows to see the README.
I'll make a working http://github.com/skilstak/boilerplate-course with the structure I'm standardizing on for SkilStak, and maybe it could at least evolve or factor into something of a bigger standard.
Speaking of standards, I would really appreciate any kind of influence anyone can bear over there at GitHub putting some wind in the sails of an official TOML Specification.. It is clearly the core of most of these hand-maintained data stores—especially the types that we are talking about. Imagine maintaining meta-data about our lessons, assignments, and courses using basic editors in TOML. (JSON has proven very unwieldy when doing this stuff by hand.)
I suggest a starting point on any kind of standard is a discussion of the domain language involved. A glossary of terms.