more extensive route rule documentation
Open
Nobody has claimed this yet.
documentation
v2
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Would be nice to have a grid/table listing support for different route rules for different providers - or maybe more detailed info so people can see what rules are currently supported or planned for different providers.
Options could be:
native- e.g. platform-implemented feature, like a redirect or header on vercel or netlify)built-in- e.g. nitro-provided caching will always work on any provider, with progressive enhancement if provider has additional featuresin-progress- e.g. vercel isrnot supported
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing route-rule documentation and locating the provider-specific support details for Vercel and Netlify. Document each rule as native, built-in, in-progress, or not supported, and make the resulting support matrix clear for current and planned behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100