4 ms·
My blog (http://blog.stargrave.org/russian/ http://blog.stargrave.org/russian/) initially also used Git as a storage, where each commit is a post, and its log m
by stargrave 4y ago
My blog (http://blog.stargrave.org/russian/ http://blog.stargrave.org/russian/) initially also used Git as a storage, where each commit is a post, and its log message is the content itself. If I add gitweb/cgit, when it will also feature web interface and Atom feed automatically. Later I added my own rendering engine to it: http://www.sgblog.stargrave.org/ http://www.sgblog.stargrave.org/ for efficiency and automatic transparent gopher/gemini protocols support. Each post also can have some dynamic tags/topics attached, that are stored in git's notes branch. And later I also added ability to leave comments, by sending email message, that is committed in another git-note branch in the form of recfile (https://www.gnu.org/software/recutils/ https://www.gnu.org/software/recutils/) plain-text comment. Everything is plain text, can be used with Git solely, but has an engine for better rendering and wider protocols support.
- bdhcuidbebe 4y ago> and its log message is the content itself That’s a curious design choice. Care to share more details, like why not commit the content? How do you deal with fixing typos?