Creating lessons by seeding is inefficient and can be troublesome with the disjoint between the seed and the lesson.
One workaround for this would be to include metadata for each lesson in the header. There are Kramdown parsers (Kramdown-metadata-parser) that are able to read this information and return a hash.
We can then use this data to dynamically seed the ruby lessons.
I'd like to test-run this type of seeding with the ruby content before rolling it out site-wide
Creating lessons by seeding is inefficient and can be troublesome with the disjoint between the seed and the lesson.
One workaround for this would be to include metadata for each lesson in the header. There are Kramdown parsers (Kramdown-metadata-parser) that are able to read this information and return a hash.
We can then use this data to dynamically seed the ruby lessons.
I'd like to test-run this type of seeding with the ruby content before rolling it out site-wide