The more capable a writing tool becomes, the easier it is for content to become trapped inside it. For a personal blog, the writing should outlive the application. This project therefore treats Markdown files as the only source of truth.
What one source means
Publishing Studio does not keep posts in a separate database and export them later. It reads and safely updates files in the site repository. Astro builds those exact same files.
| Concern | Choice |
|---|---|
| Post source | Markdown files |
| Change history | Git |
| Public result | Astro static build |
| App database | None |
What this gives me
The files remain editable in any text editor. Git shows when and why a sentence changed, and the website can be restored without Publishing Studio.
- No dependency on a particular application
- Human-readable diffs before publishing
- A clear boundary between backup and publication
What it costs
File formats and paths need strict validation. Duplicate slugs, invalid dates, and broken internal links must fail before a build reaches production. Editor conveniences also have to preserve the original text.
That constraint feels less like inconvenience and more like the cost of retaining ownership of the writing.