ノート
Rebuilding This Site with Astro and Notion
Why I moved my portfolio off Adobe Portfolio onto Astro, Tailwind, and a Notion CMS — the architecture and the trade-offs.
This site used to run on Adobe Portfolio. It was fine — until I wanted a journal, downloadable resources, proper Japanese typography, and URLs I fully controlled. So this is the third generation of mactokyo.com, and the first one I can call production engineering.
The stack is deliberately boring: Astro for static generation with almost no client JavaScript, Tailwind for styling, Notion as the CMS so publishing is editing a database row, Cloudflare R2 for permanent file URLs (Notion’s file links expire — never ship those), and Cloudflare Pages for hosting. Total monthly cost: zero.
A few decisions worth recording:
- One content model, two sources. The Astro content collections mirror the Notion schema field-for-field, so switching sources is a data swap, not a rebuild.
- Every old URL survives. Fifteen years of SEO folklore says don’t break links; the full redirect map ships as a Cloudflare
_redirectsfile. - Bilingual from the start. Japanese and English typography have different rhythm — line-height, letter-spacing, even what “bold” means. The font stack handles both natively.
The full build is open in the repository. If you’re considering the same migration, the journal will keep notes here.