PAGES KNOWLEDGE BASE

OVERVIEW

Astro page routes with i18n support, dynamic routing for blog/project/resource

STRUCTURE

1
src/pages/
2
├── blog/           # Blog posts and lists
3
├── project/        # Project showcases
4
├── resource/       # Resource collections
5
├── og/             # Open Graph image generation
6
├── zh/             # Chinese mirrored routes
7
├── en/             # English mirrored routes
8
├── index.astro     # Home page
9
└── [others].astro  # Static pages (about, friend, 404)

WHERE TO LOOK

Task	Location	Notes
Blog posts	`src/pages/blog/[...slug].astro`	Post content rendering
Blog list	`src/pages/blog/[...page].astro`	Paginated list
Project pages	`src/pages/project/`	Project routes
Resource pages	`src/pages/resource/`	Resource routes
OG images	`src/pages/og/[...slug].png.ts`	Dynamic OG generation
i18n	`src/pages/zh/`, `src/pages/en/`	Mirrored routes

CODE MAP

Symbol	Type	Location	Role
getStaticPaths	function	`src/pages/blog/[...slug].astro`	Generate post routes
getStaticPaths	function	`src/pages/blog/[...page].astro`	Generate paginated routes
OG Image	endpoint	`src/pages/og/[...slug].png.ts`	Satori-based image generation

CONVENTIONS

Dynamic routes use [...slug].astro or [...page].astro pattern.
Mirrored routes in zh/ and en/ handle localized entry points.
Static assets like robots.txt and sitemap.xml are generated via .ts endpoints.

ANTI-PATTERNS

Do not modify generated routes manually - they are auto-created.
Avoid hardcoding localized strings in .astro files.
Don’t bypass the dynamic routing logic for content collections.