Document redirect pages template pattern

[bcomnes]

Adds a "Redirect Pages" section to the Templates documentation showing how to generate meta-refresh HTML redirect pages for URL migrations using the object array template type.

The example covers:

• Generating one index.html per redirect entry with a correct meta-refresh and canonical link
• An inline escapeXml helper to prevent XSS in redirect targets
• A note on SEO implications of meta-refresh vs. server-side redirects
• A second example showing how to generate a Netlify _redirects file instead

DomStack has no built-in redirect mechanism, so this documents the idiomatic template-based approach that any migrating site would otherwise need to discover independently.

Closes #237

[coveralls]

Coverage Report for CI Build 24619424796

Coverage remained the same at 91.469%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	4070
Covered Lines:	3804
Line Coverage:	93.46%
Relevant Branches:	642
Covered Branches:	506
Branch Coverage:	78.82%
Branches in Coverage %:	Yes
Coverage Strength:	73.64 hits per line

---

💛 - Coveralls

[Copilot]

Pull request overview

Adds documentation for an idiomatic DomStack pattern to generate redirect artifacts via templates, aimed at helping users migrate URLs without built-in redirect support.

Changes:

• Adds a “Redirect Pages” documentation section with an object-array template example that generates meta-refresh HTML redirect pages.
• Adds a second example showing how to generate a Netlify/Cloudflare Pages _redirects file via a template.
• Includes an inline escaping helper and brief SEO guidance.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[bcomnes]

Addressed all four review comments:

1. Single string return wording (comment 3105658491): The Netlify example uses the single-object template type (returns { outputName, content }), not a plain string. Updated to "single-object template type".

2. escapeXml XSS claim (comment 3105658495): Narrowed the prose to say escapeXml prevents HTML injection in attribute values. Added a note that it does not block javascript: scheme URLs, and to keep redirect targets to known-safe URL patterns.

3. Section placement (comment 3105658504): Moved the Redirect Pages section from under TypeScript Support to the correct location at the end of the Templates section (after the RSS Feed example, before Global Assets).

4. Leading / in outputName (comment 3105658508): Added a warning that outputName is resolved with path.resolve, so a leading / in from values would write outside the build directory.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[bcomnes]

Ok so this doesn't actually close the upstream issue. But it is a decent docs addition.

In terms of docs, I would suggest simplifying the example and pull in common tags or something for html escaping. I would also leave out the copy directory example. Of course it works but that whole feature is just an escape hatch.
Another solution is to just make a regular page or layout and add the redirect header, keeping with the literal site layout.

We should implement the feature though but I'm not sold on the best approach.