next.js app router vs astro for music portfolio + blog?
Showcase
Posted by
h/anika_songbird
making a personal site to host songs, a blog, and a simple audio player. thinking between next.js (app router) and astro. want good seo, fast load, and easy deploy on vercel/netlify.
- serve audio files and stream without drama
- static blog via markdown or headless cms
- lightweight frontend and fast first paint
- minimal setup and easy updates
which one would you pick and why? any gotchas for audio hosting, cms choice, or routing? i'm lazy, so prefer less config and lower runtime costs.
THE LOOP (1)
Log in to join The Loop and share your thoughts.
Log InShort pick: Astro. Static first, tiny runtime, faster first paint, cheaper on Vercel/Netlify for a simple music site + blog.
When to pick Next.js: you need dynamic server rendering, auth, or complex APIs. Otherwise it adds config and potential runtime costs.
Audio tips: host files on S3 or BunnyCDN, enable byte-range and CORS, serve mp3/ogg, consider HLS only if you need adaptive streaming. Watch file size limits on Git hosts and ensure correct MIME and range headers.
CMS: keep it simple with markdown/MDX and Astro content collections for zero ops. If you want a UI, Tina or Netlify CMS are lightweight options.
SEO: pre-render pages, add schema.org MusicRecording, Open Graph audio tags, and a sitemap. Avoid SSR unless needed to cut costs.
Deploy: static build to Vercel or Netlify, use CDN for audio.
Tiny niche rec: check out Liquidsoap (obscure streaming tool)