4 ms·
I just built my own SSG using Markdown for source documents with JSON metadata as "front matter". If I ever need to switch to something else, it should be prett
by bogwog 3y ago
I just built my own SSG using Markdown for source documents with JSON metadata as "front matter". If I ever need to switch to something else, it should be pretty easy to auto-convert everything. I tried existing SSG tools (Hugo, Grav) but didn't like them. They felt too complicated, with many features I don't need or want.
I have a Tiddlywiki too for personal notes and stuff, and while the portability is great, authoring content is annoying since you pretty much need a custom application or web server to handle changes. That kills a lot of the cool factor IMO.
But I think TW would be great for documentation in a project. Instead of requiring a static site generator in my git repo to compile the docs (or just expect users to browse them via text editor), a self-contained TW would work out of the box. Small edits/contributions should also be relatively easy even without a browser plugin/app, since you could just CTRL+S and send a PR with your changes.
EDIT: although I guess reviewing a TW diff wouldn't be easy, at least in the typical Github/Gitlab UIs
- bthallplz 3y agoTiddlywiki's markup language makes portability a bit more difficult, so it's likely a good thing that you shifted to fully using Markdown. (You can use markdown in Tiddlywiki, but I think that adds an extra step to the authoring process (selecting the language for each tiddler).) I moved away from using TW for personal stuff because its authoring interface was too disconnected from where I primarily take and consume notes (mobile). I use mostly Obsidian now + SSG for website generation. If you use the Tiddlywiki NodeJS version, each tiddler is stored as a separate file, allowing them to be easily version controlled for a documentation project.