Core Structure

Outbound

Derives navigation targets and navigation behavior.

Navigation behavior is determined by two complementary layers:

Locale Carrier

Defines how locale information is represented in navigation URLs.

Supported carrier types include: path | host | query.

For configuration details, see: localeCarrier

When using host, an explicit locale-to-host mapping is required, see: host

A navigation intent is composed of a Destination and a Locale.

Depending on the tool, the destination may appear as href, url, or similar.


1. Destination only

When only a Destination is provided, the current locale is preserved.

Input
Destination: "/fr/about"

Result
"/en" → "/en/about"

Even if the Destination contains a locale segment, the locale will not change unless it is explicitly specified.

2. Locale only

When only a Locale is provided, the locale is switched on the current path.

Input
Locale: "fr"

Result
"/en" → "/fr"

3. Destination and Locale

When both Destination and Locale are provided, a complete and explicit navigation result is produced.

Input
Destination: "/about"
Locale: "fr"

Result
"/en" → "/fr/about"

A Destination may use the {locale} placeholder to explicitly describe the locale position within the path, avoiding ambiguity between locale and actual path segments.

Input
Destination: "/admin/{locale}/about"

Result
"/admin/en" → "/admin/en/about"

This form helps keep the structural meaning of the destination explicit.

Integration

Intor provides framework-specific navigation tools to apply Outbound Routing behavior.

For framework-specific integration details, see: Frameworks

On this page