docs: #291 document encoding expectations for frontmatter values and dynamic route params - #292
Open
jstockdi wants to merge 1 commit into
Conversation
…tter values and dynamic route params
4 tasks
✅ Deploy Preview for super-tapioca-5987ce ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
thescientist13
requested changes
Aug 6, 2026
thescientist13
left a comment
thescientist13
left a comment
Member
There was a problem hiding this comment.
I would like to avoid using LLM output for documentation, if we could. Unlike code, documentation is direct communication to our users, and so emdashes and "robotic" language (obvious signs of LLM usage) is not something I feel good about publishing.
Documentation should be for developers by developers. Could you please re-write using your own words please?
Thanks!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #291 — documents the encoding expectations for frontmatter values and dynamic route params, per the discussion on ProjectEvergreen/greenwood#1710.
Changes
/docs/content-as-data/frontmatter/): new "Special Characters" section — a literal%passes through to the output verbatim, percent-encoded values decode once, and the same rules apply to pages from source plugins so both content APIs behave identically./docs/pages/server-rendering/): note under Dynamic Prerendering —getStaticPathsparam values round-trip decoded (spaces, non-ASCII, literal%), while emitted folder names are percent-encoded to stay URL-safe.Timing
The documented behavior lands in the CLI with ProjectEvergreen/greenwood#1710 and ProjectEvergreen/greenwood#1714, so this should merge alongside or after the release line that includes them.