Astro Series Day 27: View Transitions
This chapter covers Astro 3.0's View Transitions — enabling app-like smooth transitions for static sites. The API is experimental; details follow.
This chapter covers Astro 3.0's View Transitions — enabling app-like smooth transitions for static sites. The API is experimental; details follow.
Building websites often focuses too much on technical aspects and lacks ideas for running a site or product; here I add my process preparing to blog.
A CMS helps author and manage site content and assets; features include scheduling, editors, collaboration, and asset management.
I use ESLint and Prettier with TypeScript and VSCode enhancements to keep code consistent and error-free. This post shows how I added them to my Astro blog.
As projects grow, relative import paths become hard to read and maintain. This post shows how to set path aliases in Astro via the TS config.
Environment variables let you avoid hardcoding, and securely store secrets (API keys, DB passwords). Astro uses Vite under the hood.
Overview of common Astro features and deploying your finished site. So far, the series has used Astro for static site generation.
Previously I built an RSS via a static endpoint as a simple exercise; I go further by building a collection of data to build a collection-based post search.
Covers creating endpoints in Astro and generating an RSS XML file, building on prior lessons about Markdown/MDX and content collections.
Learn to organize content collections and auto-generate category pages so posts can be grouped and browsed by category.
Generating routes dynamically from content collections is convenient, but when items grow you should paginate them. Astro's built-in pagination helps.
Astro Content Collections (since 2.0) provide local content management and automated type validation—ideal for injecting many files into a site.
Covers how to set up layouts for Markdown/MDX files—templates to manage common page patterns, reduce duplication, and centralize page structure.
Images often accompany content and can dominate a page's compute and bandwidth. Astro provides components to help.
Is it possible to update page content without touching code, simply by editing documents? In other words, separating content from layout and logic.