Tag: astro

17 articles

· astro / ssg

Astro 5 review — what changed and whether to upgrade

Upgrade Astro 4 now. Content Layer delivers 5× faster Markdown and 25–50% less memory. Hold if you use @astrojs/lit or need Cloudflare adapter v13+ features.

· deno / fresh

Deno Fresh vs Astro — which framework wins in 2026?

Astro is the safer default for most sites in 2026. Fresh 2.x wins on edge cold-start if your team lives in Deno — but ecosystem immaturity is the real cost.

· static-sites / astro

Best static-blog stack in 2026

Astro 6.4 is the right default for most static blogs: best DX, built-in i18n, zero JS shipped by default, and Content Layer API makes large Markdown sites fast. Hugo wins if you have 10k+ pages or non-negotiable CI speed. Skip Gatsby entirely.

· seo / i18n

i18n SEO pitfalls — hreflang and the slug parity trap

One slug typo silently breaks your entire hreflang graph — no build error, no browser warning. Here is what actually breaks and how to catch it before rankings drop.

· astro / pagefind

How to add full-text search to an Astro site with Pagefind

Add zero-infra full-text search to any Astro static site using Pagefind 1.5: install, build integration, Component UI, data attributes, CSP, and deploy.

· rss / astro

RSS as a distribution channel — still worth it in 2026?

Yes — RSS earns its 15-minute setup cost in 2026. Social organic reach has collapsed to 2–5%; RSS delivers to 100% of subscribers with no algorithm in the way.

· astro / mdx

How to Add MDX to Astro 5 Content Collections

Step-by-step guide to installing @astrojs/mdx and wiring it into Astro 5 Content Layer API — typed frontmatter, component imports, and every pitfall documented.

· astro / mdx

How to write good Astro frontmatter (and validate it)

Add a Zod schema to src/content.config.ts. Frontmatter fields get TypeScript types and build-time validation — no extra dependencies, no runtime surprises.

· astro / rss

How to Build an RSS Feed in Astro with @astrojs/rss

Add an RSS feed to your Astro site using @astrojs/rss — covers content collections, rssSchema, auto-discovery, full-post content, and W3C validation.

· cms / headless-cms

Best Headless CMS for Developers 2026: Sanity, Strapi & More

Sanity is the default SaaS pick; Strapi and Payload own the self-host tier. When each of the five contenders wins — and why Contentful dropped out.

· rendering / nextjs

Static vs dynamic rendering in 2026: pick your mode

The SSG-vs-SSR binary is obsolete. Six rendering modes now cover the full spectrum — here is which one fits your use case, with benchmarks and code.

· astro / i18n

How to build a multilingual Astro site (EN + VI)

Build an EN+VI Astro 5 site using built-in i18n routing: content collections, locale pages, language switcher, hreflang, and Cloudflare Workers deploy.

· astro / astro-6

Astro 6 Review: What's New, What Breaks, and When to Upgrade

Astro 6 is worth upgrading to. Node 22 is required, legacy Content Collections are gone, Zod 4 silently breaks schemas. Here is exactly what breaks.

· astro / cloudflare

How to Deploy an Astro Site on Cloudflare Pages: Setup Guide

Cloudflare Pages deploys Astro for free with unlimited bandwidth. Step-by-step: adapter install, monorepo root directory fix, env vars, and custom domain.

· astro / eleventy

Astro vs Eleventy — content sites in 2026

Astro is the right default for TypeScript teams building content sites with CMS integration or interactive islands. Eleventy wins when build speed, zero-JS output, or maximum config freedom are non-negotiable.

· astro / hugo

Astro vs Hugo — TypeScript ergonomics vs raw speed

Pick Astro for TypeScript teams and interactive components. Pick Hugo if build time is the hard constraint at 10K+ pages. Here is where the line sits.

· nextjs / astro

Next.js vs Astro 2026 — when to choose static sites

Pick Astro for content-heavy sites that need minimal JavaScript and real Core Web Vitals. Pick Next.js when you are building an app, not a site.