-
Notifications
You must be signed in to change notification settings - Fork 16
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: sidebar restructure #644
Conversation
✅ Deploy Preview for pomerium-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, I think this is a good change.
- I think we should move “Clients” from under “Pomerium core” to being under “Deploy” at the bottom of the list.
- Move “To production” from Enterprise to under Deploy and move it to the very bottom of the list.
Otherwise, LGTM pending … yeah, that’s going to be a lot of redirects. :/
static/_redirects
Outdated
@@ -336,7 +336,7 @@ https://0-20-0.docs.pomerium.com/category/guides https://0-20-0.docs.pomerium.co | |||
# flattened the changelog, and upgrading guide | |||
/docs/overview/upgrading/archive /docs/overview/upgrading | |||
/docs/overview/changelog/archive /docs/overview/upgrading | |||
/docs/overview/upgrading /docs/releases/upgrading | |||
/docs/overview/upgrading /docs/deploy/core/upgrading |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we set a catch all for /deploying/*
and /releases/*
?
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-0-22-0 0-22-0
# Navigate to the new working tree
cd .worktrees/backport-0-22-0
# Create a new branch
git switch --create backport-644-to-0-22-0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick --mainline 1 a94e5e54c90158ea7caf65c8001671b5733510b2
# Push it to GitHub
git push --set-upstream origin backport-644-to-0-22-0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-0-22-0 Then, create a pull request where the |
This PR replaces
/docs/releases
with/docs/deploy
. The Deploy sidebar houses the following sections: