I migrated my blog to mdorigin. With AI, I feel like I can revive my blog.

I told Codex, "Based on my content, recommend a blog style for me."
Codex provided me with two versions, opened two ports for preview, and explained the reasons clearly.
So I deleted the built-in template style system of mdorigin. Templates are originally a product of the pre-Agent era, mainly to lower the barrier to changing styles.
Now that we have Agent, providing extension capabilities is enough. The site style can be customized by Agent, and mdorigin only handles the HTML / Markdown structure, routing, and content retrieval.
A problem I used to have when writing blogs: many systems require images and attachments to be stored in a separate public directory.
This makes deployment easier, but writing feels awkward. An article has one set of paths, images have another, and the local preview and the final published view are not the same.
mdorigin will keep images, videos, and attachments together with the article.
Use relative paths directly in Markdown.
When publishing, mdorigin will automatically route media files to Cloudflare's asset or object storage based on their size, and resource paths on the page will also be relative paths.
Currently, my blog is just a public directory of my local Obsidian workspace, and mdorigin just needs to publish this directory.