Routes and locales reference

This table is the current route-family reference. It describes a route shape, not permission to claim every future slug is collision-free.

search is a built-in path. Within a collection, tags, page, and feed.xml have dedicated meanings. Archive, pagination, tag, and feed rules can therefore shadow names that would otherwise look like ordinary slugs. Pick collection type names and common slugs before a large content migration, then build and inspect the relevant route family.

Locale variants

Declare the default and supported locale set in .web/site.yaml:

locale: en
locales:
  - en
  - zh

Then use sibling locale variants only where content changes:

The runtime can derive a compatibility locale set from .aup/locales/*.json when locales is absent. A new site should declare the actual supported set in site.yaml; it gives authors, build, and review one explicit contract. Do not add en/ and zh/ directories under every page/object to create translations of the same thing.

Navigation is not routing. A menu link does not create a page, and a page directory does not decide which menu should expose it. Resolve the route first, then make a separate information-architecture choice for navigation.

For a walkthrough, read Routes, navigation, and locales.