Skip to content
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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Propose navigation updates #16718

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 26 additions & 26 deletions docs/mint.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,9 +53,9 @@
"group": "Get started",
"pages": [
"v3/get-started/index",
"v3/get-started/whats-new-prefect-3",
"v3/get-started/quickstart",
"v3/get-started/install",
"v3/get-started/quickstart"
Copy link
Contributor

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.

#16705

"v3/get-started/whats-new-prefect-3"
],
"version": "v3"
},
Expand Down Expand Up @@ -101,7 +101,8 @@
"v3/develop/visualize-flow-structure",
"v3/develop/big-data",
"v3/develop/cli-shell",
"v3/develop/secrets"
"v3/develop/secrets",
"v3/develop/test-workflows"
],
"version": "v3"
},
Expand Down Expand Up @@ -145,8 +146,7 @@
"v3/develop/settings-and-profiles",
"v3/develop/settings-ref"
]
},
"v3/develop/test-workflows"
}
],
"version": "v3"
},
Expand All @@ -156,7 +156,7 @@
"v3/deploy/index",
"v3/deploy/run-flows-in-local-processes",
{
"group": "Run flows on dynamic infrastructure",
"group": "Run on dynamic infrastructure",
"pages": [
"v3/deploy/infrastructure-concepts/work-pools",
"v3/deploy/infrastructure-concepts/workers",
Expand All @@ -169,18 +169,12 @@
"version": "v3"
},
{
"group": "Dynamic infrastructure examples",
"group": "Infrastructure examples",
Copy link
Contributor

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.

Copy link
Contributor Author

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...

"pages": [
"v3/deploy/infrastructure-examples/managed",
"v3/deploy/infrastructure-examples/serverless",
"v3/deploy/infrastructure-examples/docker",
"v3/deploy/infrastructure-examples/kubernetes"
],
"version": "v3"
},
{
"group": "Static infrastructure examples",
"pages": [
"v3/deploy/infrastructure-examples/kubernetes",
"v3/deploy/static-infrastructure-examples/docker"
],
"version": "v3"
Expand All @@ -194,10 +188,16 @@
"pages": [
"v3/automate/index",
"v3/automate/add-schedules",
"v3/automate/events/events",
"v3/automate/events/automations-triggers",
"v3/automate/events/custom-triggers",
"v3/automate/events/webhook-triggers"
{
"group": "Prefect events",
"pages": [
"v3/automate/events/events",
"v3/automate/events/automations-triggers",
"v3/automate/events/custom-triggers",
"v3/automate/events/webhook-triggers"
],
"version": "v3"
}
],
"version": "v3"
},
Expand Down Expand Up @@ -232,15 +232,15 @@
],
"version": "v3"
},
"v3/manage/self-host"
],
"version": "v3"
},
{
"group": "Migrate",
"pages": [
"v3/resources/upgrade-to-prefect-3",
"v3/manage/self-host",
{
"group": "Migrate",
"pages": [
"v3/resources/upgrade-to-prefect-3",
"v3/resources/upgrade-agents-to-workers"
Comment on lines +239 to 240
Copy link
Contributor

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).

],
"version": "v3"
}
],
"version": "v3"
},
Expand Down
Loading