This showcase retains explicit legacy-address rules in static/_redirects, copied to the build output root. They are showcase host configuration, not a built-in MarkStack redirect engine. The table below represents all 56 declarations in the retained file. Root / stays the homepage; it has no self-redirect declaration.
All destination links point to root-relative V2 handbook routes; use the link target for the exact destination path. Each rule uses 301. Slash and non-slash variants are explicit declarations, not evidence that every possible legacy spelling is known.
Source paths below are split by base to fit phones. Join the named base and suffix exactly. “(base without slash)” means the base itself; / means its slash form. No spaces are part of a source path.
The official Pages redirects documentation describes a plain-text _redirects file in the deployable static output. Each line is source destination code; comment lines start with #. Pages parses the file rather than serving it as a static asset. The provider default is 302 when no code is supplied; these declarations explicitly select 301.
Rules apply to static asset responses, not requests handled by Pages Functions. For a Function-owned route, implement the required behavior in the Function or exclude it from Functions. MarkStack’s disposable preview server does not execute these redirect rules, and other hosting products need their own configuration.
Place static rules before dynamic rules. A destination can include a fragment, but a source fragment is browser-side and not matched by the network. Do not replace this explicit map with a broad homepage fallback: unknown addresses should return a real 404, not silently become home. Permanent redirects can be cached, so inspect a proposed mapping before release.
Local build-target validation can verify destinations, but not provider rule application. Recheck every declaration on the deployed host after release, including final content and redirect chains. A prior host result is not proof a later deployment kept the file, static routing or correct destinations. When an old live address is discovered outside this file, verify its intended replacement before adding a rule.
The provider mechanics above were checked against its official page on 12 October 2026. There is no new live redirect certification attached to this unpublished draft.
