After Building My Own Blog, the Lasting Asset Was the Writing, Not the Framework
A look back at Toris Blog, which started on Next.js, and the current Astro structure, and why keeping markdown, URLs, and metadata matters more than swapping technology.
Joohwan Yu · Founder, Full Stack Developer
Toris · Published
Contents
Toris Blog is a blog that started on Next.js. The structure of toris.kr as I checked it now is Astro, which reads markdown files as a content collection to build post pages. Looking at the two points in time side by side makes clear what the lasting asset is. Even if the rendering tool changes, the writing and the addresses have to carry on.
The context for choosing file-based content
At first, what I liked was that I could manage posts in the same editor and Git I use for development. I didn’t have to switch to a separate admin screen, and I could view the edit history of sentences like code. That simplicity suited a blog that I write and run alone.
In exchange, changing a post requires a build and a deployment. If the number of authors grows or the editorial approval flow gets complicated, file-based alone may become inconvenient. It’s also not accurate to say there’s no operating cost just because there’s no database. The cost has moved from running a server to the publishing procedure.
The contract I can confirm in the current code
Currently the post ID is created from the markdown file name, and the detail address is generated as /posts/<slug>. Changing a title and changing a file name are not the same task. Renaming a file can be tied to the address, so I have to check existing links first.
Metadata such as title, description, and date is also managed together with the body. Even if the body is good, if the description in the list is empty or the date is wrong, browsing and feed ordering feel off. A single post includes not just the body but also the information that appears in the list, search, and share views.
Criteria for evaluating a technology swap
Changing the framework doesn’t by itself make a better blog. What’s needed is that readers arriving at the existing addresses can read the same posts, that the RSS and sitemap carry over, and that code and tables display properly. The current repository also has verification code that compares the original posts with the built pages.
If I rebuilt the blog, before bending the content to fit a new tool I would first write down the contract to keep. Even if it’s a space for experimenting with technology, readers have a promise tied to addresses I’ve already shared. Recording the reason for choosing a framework together with the assets that must be preserved on top of it made for a retrospective I could use for longer.
Related post: Retrospective on first building Toris Blog
Advertisement