weaversa

When I run it, it seems to put 2 copies of the template at the bottom of each lab.

So, all future development would happen in layercake/layercake/templates, and we would run the script before merging into master? Or, is this just a one-time thing?

> Do you see any discrepancies? If the duplication wasn't there, it would be easy to `diff` the before and after files. :-)

I agree that we should serve from a dedicated branch rather than from master, and we can setup a GitHub action to keep that branch up to date whenever a...

Well, what if we made a release branch and just update it manually when we push out new releases?

Is there some way to get the docs readme to point to the raw sgv rather than `https://github.com/weaversa/cryptol-course/blob/docs/misc/CryptolCourse.gv.svg`, like in the master branch? This way the image stays clickable. Also,...

Great work! This is all amazing!

Could we have the master branch be a version of the docs branch for github browsing and a docs/release branch for vscode etc?

And development would merge to on a devel branch and master/docs/html are all deployed from that?

I see. So we could instead have the base README point into the docs directory (or some similar thing) for folks to start the class if they want to view...