move some things around for launch (#1436)

Author: abelanger5

frontend/docs/pages/home/_meta.json

@@ -19,7 +19,6 @@
   "your-first-task": "Tasks",
   "workers": "Workers",
   "running-your-task": "Running Tasks",
-  "orchestration": "Workflow Orchestration",
   "environments": "Environments",
   "--running-workflows": {
     "title": "Ways of Running Tasks",
@@ -44,23 +43,24 @@
     "title": "Workflows",
     "type": "separator"
   },
+  "orchestration": "Task Orchestration",
   "dags": {
     "title": "Directed Acyclic Graphs (DAGs)"
   },
+  "conditional-workflows": "Conditional Workflows",
   "child-spawning": {
     "title": "Child Spawning"
   },
   "additional-metadata": {
     "title": "Additional Metadata"
   },
-
   "--error-handling": {
     "title": "Error Handling",
     "type": "separator"
   },
   "timeouts": "Timeouts",
   "on-failure-tasks": "On Failure Tasks",
-
+  "bulk-retries-and-cancellations": "Bulk Retries and Cancellations",
   "retries": {
     "title": "Retries"
   },
@@ -85,7 +85,6 @@
   },
   "docker": "Running with Docker",
   "worker-healthchecks": "Worker Health Checks",
-
   "--flow-control": {
     "title": "Flow Control",
     "type": "separator"
@@ -110,24 +109,17 @@
     "title": "Bulk Cancellation",
     "display": "hidden"
   },
-  "--v1-new-features": {
-    "title": "V1 New Features",
-    "type": "separator"
-  },
-  "v1-new-features-overview": "Overview",
-  "v1-complex-workflows": "Complex Workflows",
   "v1-durable-execution": {
     "title": "Durable Execution",
     "display": "hidden"
   },
-  "v1-bulk-operations": "Bulk Cancel and Replay",
-  "v1-sdk-improvements": {
-    "title": "SDK Improvements"
-  },
   "--v1-migration-guides": {
     "title": "V1 Migration Guides",
     "type": "separator"
   },
+  "v1-sdk-improvements": {
+    "title": "SDK Improvements"
+  },
   "migration-guide-engine": "Engine Migration Guide",
   "migration-guide-python": "Python Migration Guide",
   "migration-guide-typescript": "Typescript Migration Guide",

frontend/docs/pages/home/v1-bulk-operations.mdx renamed to frontend/docs/pages/home/bulk-retries-and-cancellations.mdx

@@ -65,8 +65,6 @@ The first way to bulk cancel or replay runs is by providing a list of run ids. T
 
 ### Bulk Operations by Filters
 
-### Bulk Operations by Run Ids
-
 The second way to bulk cancel or replay runs is by providing a list of filters. This is the most powerful way to cancel or replay runs in bulk, as it allows you to cancel or replay all runs matching a set of arbitrary filters without needing to provide IDs for the runs in advance.
 
 <UniversalTabs items={["Python"]}>

frontend/docs/pages/home/v1-complex-workflows.mdx renamed to frontend/docs/pages/home/conditional-workflows.mdx

@@ -11,25 +11,11 @@ export const SimplePy = {
 
 export const getStaticProps = ({}) => getSnippets([SimpleTs, SimplePy]);
 
-# What is Orchestration?
+# Task Orchestration
 
-Orchestration can be very overloaded in the software development world. In Hatchet, we define orchestration as the both process of coordinating the execution of tasks on "compute" and the coordination of the compute resources themselves.
-
-## Orchestrating Tasks
-
-In Hatchet there are two primary ways to orchestrate tasks:
+Not only can you run a single task in Hatchet, but you can also orchestrate multiple tasks together based on a shape that you define. For example, you can run a task that depends on the output of another task, or you can run a task that waits for a certain condition to be met before running.
 
 1. [Declarative Workflow Design (DAGs)](./dags.mdx) -- which is a way to declaratively define the sequence and dependencies of tasks in a workflow when you know the dependencies ahead of time.
 2. [Procedural Child Spawning](./child-spawning.mdx) -- which is a way to orchestrate tasks in a workflow when you don't know the dependencies ahead of time or when the dependencies are dynamic.
 
-## Orchestrating Tasks With Flow Controls
-
-In addition to coordinating the execution of tasks, Hatchet also provides a set of flow control primitives that allow you to orchestrate tasks in a workflow.
-
-1. [Worker Slots](./workers.mdx#understanding-slots) -- which is a way to control the number of tasks that can be executed concurrently on a given compute process.
-2. [Concurrency Control](./concurrency-keys.mdx) -- which is a global way to control the concurrent execution of tasks based on a specific key.
-3. [Rate Limiting](./rate-limits.mdx) -- which is a global way to control the rate of task execution based on time period.
-
-## Orchestrating Compute
-
-In addition to coordinating the execution of tasks, Hatchet also coordinates the compute resources themselves. Autoscaling compute resources to match the workload is a core feature of Hatchet managed compute and we're working on plugins for other compute orchestrators.
+To read about waiting on additional conditions in a workflow, see the [Conditional Workflows](./conditional-workflows.mdx) guide.