executable-tutorials
markright
| executable-tutorials | markright | |
|---|---|---|
| 3 | 1 | |
| 51 | 5 | |
| - | - | |
| 0.0 | 0.0 | |
| about 3 years ago | about 2 years ago | |
| JavaScript | ||
| - | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
executable-tutorials
-
Runme – Interactive Runbooks Built with Markdown
See also, executable-tutorials:
https://github.com/dharmatech/executable-tutorials/blob/main...
- Executable Tutorials
markright
-
Executable Tutorials
I'm exploring something along these lines in my (now mostly dormant) project called 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. 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.
What are some alternatives?
runme - DevOps Workflows Built with Markdown
crossnote-app - 📝 An interesting markdown note taking application
xc - Markdown defined task runner.