-
Notifications
You must be signed in to change notification settings - Fork 15.4k
Render Netlify redirects from page aliases #53396
Copy link
Copy link
Labels
area/web-developmentIssues or PRs related to the kubernetes.io's infrastructure, design, or build processesIssues or PRs related to the kubernetes.io's infrastructure, design, or build processeskind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Metadata
Metadata
Assignees
Labels
area/web-developmentIssues or PRs related to the kubernetes.io's infrastructure, design, or build processesIssues or PRs related to the kubernetes.io's infrastructure, design, or build processeskind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
This is a Feature Request
What would you like to be added
Update
layouts/index.redirectsto support Hugoaliases(in the page front matter). After the change, we would implement Hugo aliases by rendering them to Netlify redirects.Why is this needed
If we do this, we can automate more of how redirects work.
/xx/docs/to/xx/docs/home/is automatic(aside) If we want to, we have the option to support a different mechanism (think
<meta http-equiv="refresh" content="0;url=http://localhost:1313/example" />) for local previews. Automating even that choice is feasible.Comments
See https://honnef.co/articles/generating-netlify-_redirects-from-hugo/ for a basic implementation.
Ours needs to cover:
/ko/docs/home/(instead, that'd be a build error)Edit Also see #53396 (comment)
/area web-development