Website data strategy
Just spent several hours deleting all my open mobile tabs and loosely transferring them to markdown notes. I had over 286 tabs that I kept, and probably a least a dozen that I just deleted.
The plan
I’m planning on using Obsidian as my (interim?) post-management application. The resulting markdown files will be converted prettied-up HTML pages via 11ty and the statically hosted.
After wasting a bunch of time researching I’ve settled on this workflow because:
- Obsidian an unobtrusive mobile writing environment, and less friction means more writing.
- It stores notes in Markdown, which is great for Eleventy integration.
- Syncing between desktop and mobile with Obsidian is…better than some other options.
Far-fetched futures
I’ve started seeing little peeks of relational or graph concepts as I’ve been wrangling links and posts, and I think it would be interesting to have some kind of “PKM system as a single database” thing and shove everything into a DuckDB or Kuzu file, but that’s for another time.
For now, the fact that Markdown files allow metadata is enough for me to at least sketch out some basic connections between ideas and think loosely about what kind of “entities” I might want to land on one day (e.g. posts, links, …collections? topics?).
Some other notes
- Moving those URLs to Obsidian kinda sucked. Immensely repetitive, and they didn’t even end up in the final format—I’ll need to do some post processing to get the correct tags, titles, and other attributes.
- I’m gonna need a ton of tags eventually. I guess part of the “gardening” will be figuring out how to organize stuff.