I'm exploring something along these lines in my (now mostly dormant) project called MarkRight: https://github.com/tomashubelbauer/markright https://github.com/t

I'm exploring something along these lines in my (now mostly dormant) project called MarkRight: https://github.com/tomashubelbauer/markright https://github.com/tomashubelbauer/markright The idea is that for didactic resources (be it documents, tutorials or even small pieces of software), your prose and code are both included in a MarkDown file and fenced code blocks are used to designate creation, altering and deletion of files. Other files that get created when "running" the MarkRight document are artifacts (the source code, the compiled executables, graphics etc.), but the document is a single source of truth. Examples: https://github.com/TomasHubelbauer/markright/edit/master/example/feature-showcase/readme.md https://github.com/TomasHubelbauer/markright/edit/master/exa... I recommend still keeping those in version control for online viewing in GitHub. I have not built anything cool with MarkRight yet, but I think the idea has potential. Curious what others think.