My Current View
For a personal portfolio + knowledge site like Suengj Note, a static Markdown repository with a thin presentation layer (Astro) is the right V1 architecture — not a CMS, database, or SaaS knowledge dashboard.
Git provides audit history, diffable content, and zero server maintenance. The UI stays a portfolio first; notes and research are published artifacts, not a productivity app.
Supporting Evidence
- Content and presentation separation matches how I actually write (Markdown in editor, not forms)
- GitHub Pages deploys reliably without backend ops
- AI-assisted drafts fit naturally as file edits with human review before merge
- Scope control — no feature creep into analytics dashboards or newsletter funnels
Counterarguments
CMS tools win on collaboration UX and full-text search out of the box. If Suengj Note needed multi-author daily publishing, I'd reconsider. For single-author curated identity + notes, static wins.
Related
- Python Basic note — same Git-first philosophy for teaching repos
- Suengj Note README and CONTENT_MODEL.md
Counterarguments
- CMS search and WYSIWYG editing are faster for non-technical authors.
- Git-based workflows exclude collaborators without version control comfort.