-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Propose navigation updates #16718
base: main
Are you sure you want to change the base?
Propose navigation updates #16718
Conversation
cc @discdiver for review as well |
"v3/get-started/install", | ||
"v3/get-started/quickstart" |
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.
I recently merged a PR to move the quickstart to the end of this group so that the schedule tutorial shows up next in the logical flow. I think that makes more sense than having the installation page follow.
@@ -169,18 +169,12 @@ | |||
"version": "v3" | |||
}, | |||
{ | |||
"group": "Dynamic infrastructure examples", | |||
"group": "Infrastructure examples", |
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.
I'm okay with merging the two groups, but if we're going to do this we should also collapse the /v3/deploy/infrastructure-examples
and v3/deploy/static-infrastructure-examples
folders.
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.
Oh wait I meant to do that...
"v3/resources/upgrade-to-prefect-3", | ||
"v3/resources/upgrade-agents-to-workers" |
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.
I'm okay with nixing the top-level Migrate section, but I'd argue that the Prefect 3.0 upgrade guide belongs under Develop (since it's more code focused) and the upgrade agents to workers guide belongs under Operate (since it's more infra focused).
I like the idea of simplifying the top-level nav. Would be interested to see a preview deployment, but that's not building because of the conflicts in mint.json. |
Proposing to make the following changes to streamline the left hand nav of the docs and make it a little more compact:
I propose @daniel-prefect reviews this to agree or disagree with any/all of these changes
Checklist
<link to issue>
"mint.json
.