-
Notifications
You must be signed in to change notification settings - Fork 27.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Docs] Add example for headers
#15073
Comments
Hey @lfades could you assign this to me? I can work on this! :) |
@robintom I would love to work on this if you didn't start yet. |
@ekhattak Sorry, i did already start working on it. I will be making a PR soon. |
@robintom If possible please make a PR per example, don't merge all of them on a single one. |
This PR adds example for #15073 > - [ ] `rewrites` For [docs/api-reference/next.config.js/rewrites.md](https://github.com/vercel/next.js/blob/canary/docs/api-reference/next.config.js/rewrites.md)
This PR adds example for #15073 > - [ ] `redirects` For [docs/api-reference/next.config.js/redirects.md](https://github.com/vercel/next.js/blob/canary/docs/api-reference/next.config.js/redirects.md)
headers
Looks like these are all complete now, closing 👍 |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Documentation for custom routes was released some days ago (#14887). We should also add one example for every documentation page to better show how it works.
The following three examples are required:
rewrites
For docs/api-reference/next.config.js/rewrites.mdredirects
For docs/api-reference/next.config.js/redirects.mdheaders
For docs/api-reference/next.config.js/headers.mdEvery example should contain very basic content and focus only on the feature it's about, showing how it works for multiple use cases that are currently not covered by the documentation. After the example is complete, add a link to it at the beginning of the page in docs.
Feel free to open a PR and I'll review it asap.
The text was updated successfully, but these errors were encountered: