markright VS privatize

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.

I partially encrypt/decrypt a file based on the presence of special HEREDOCs (ie <The tool is still a WIP as it isn't portable between machines -- https://github.com/higgins/privatize

more on it here: https://encapsulate.me/writing/Privatize.html

Yes!

I keep a daily log tracked in git. All of it public although some information is encrypted with my privatization tool (https://github.com/higgins/privatize).

The log itself is a simple org file but I parse and render it in html here so that I can share important event dates (eg: my wedding) with my family and friends.

Here is what I did yesterday:

ooo, good call out. thanks!

currently i only have one warning in place if I forget to close there heredoc: https://github.com/higgins/privatize/blob/main/index.js#L168

but could add some more error checking. added to TODOs: https://github.com/higgins/privatize/commit/9696f30576897898...

https://github.com/higgins/privatize

When added to a git repo, it will automatically transparently encrypt/decrypt files you want privatized.

For example if you configured your repo to privatize the file `example.txt`, you could write:

```