CMS rambling
2024-11-10So my thinking is to maybe have some sort of CMS (probably strapi), and then to use that for this blogs content (for starters). Thinking that could be a nice replacement for my old WP blog.
Then I could write and write with nary the slightest worry in the world! For one, the quite possibly random content doesn't get committed to a VCS, so that's nice (in case I say something incredibly stupid and want to easily retract my words! I could always force push... hmmm, there truly is a world of opportunity out there). On the other hand, storing the content in a VCS will also let me time travel!
Points against CMS:
- I'd have to host a CMS... >:(
- Another moving piece of machinery! (it
couldwill break at some point and require more maintenance) - kinda KISS for a blog with no two-way communication to simply generate everything at build time from source 😌
- Whenever I scaffold something "bigger" for the sake of future unknown usage patterns, it always falls flat!
- CMSes are good for dynamic data, but do I really want to do dynamic data?! (I don't want to make my blog into a job! I just want to occasionally rant into the void)
Points for CMS:
- CMSes could be simple!
- Separate concerns: Content is content 👏, and presentation is presentation! 👏
I'll leave room for future me to make some choices here.