The Devlog Is Live: From Markdown to the Website

Why do this?

In past versions, update information was scattered across multiple channels, making it difficult for players to quickly find "what was changed this week" on the site. This leads to two problems:

• New players only saw the game entrance and no evidence of continued iteration of the project.
• When old players want to review historical changes, the path is unstable and the cost of information retrieval is high.

Therefore, we build the developer blog as a long-term content layer within the site, rather than a temporary announcement.

What is included in this edition?

• Added `/devlog` list page, which can be filtered by `game_id`.
• Added `/devlog/<slug>` details page to support displaying author, release time, and text content.
• Added "Developer Log" entry on the home page.
• A new "Development Log" entry has been added to the game homepage, which will enter the current game log list by default.

Writing method (Front Matter + Release Script)

This version does not introduce the web backend and continues to follow the "reproducible and auditable" release link:

• The author writes logs in the warehouse `docs/devlogs/posts/*.md`.
• Front Matter declares structured fields (`slug/game_id/author_id/published_at`, etc.).
• Use `node scripts/devlog-publish.js` to perform field verification and upsert to D1.

The advantage of this is that every log change is recorded in Git, and when problems occur, they can be quickly located and rolled back.

Follow-up plan

• Added author page aggregation (browse by author dimension).
• After adding more games, connect to the same log model and reuse the filtering entrance.
• Supplement structured SEO information and pre-review self-check scripts based on log pages.