Redirects

redirect can be set in .config.yml (directory-level) or in Markdown frontmatter (page-level).

Directory redirect

Commonly used to redirect a collection's root path to a specific doc:

# content/en-US/.config.yml
navigation:
  hidden: true
redirect: /introduction

Visiting /en-US automatically jumps to /en-US/introduction.

Page redirect

---
redirect: /en-US/guide/routing
---

How redirect targets resolve

• Absolute protocol links (e.g. https://..., mailto:...) are kept as-is.
• Paths starting with / are resolved from the current collection base. For example, writing redirect: /introduction in a collection whose base is /en-US resolves to /en-US/introduction.
• Paths without a leading / are resolved relative to the current directory. For example, in content/en-US/guide/.config.yml, writing redirect: test resolves to /en-US/guide/test.
• If the target already includes the base prefix, it isn't added twice.

The framework collects redirect rules across the whole workspace at build time. If the same source path has conflicting targets, it throws an error so you catch the misconfiguration early.