Docs Updates #3 - Cleanup "Product" Language (#668)

* update all dependencies

* add packageManager back

* remove hardcoded url

* wip

* cleanup from review

* cleanup again

* switch to json for storing redirects

* convert to ts

* cleanup

* ai cleanup

* Update README.md

* backfill all ids

* feat(nav): rename Connect→APIs, Automate→Flows, Manage→Hosting

* feat(llms): rename guide section titles to APIs and Flows

* docs: replace branded "Directus Connect"/"Directus Automate" with APIs/Flows

* docs(homepage): drop Data Engine/Data Studio framing

* fix: fold 11.integrations into 12.integrations to clear numeric collision

* fix sidebar

* docs(nav): rename Guides→Guide, Hosting→Deploy

* kill editor and explorer

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* fix: simplify redirect and stable id tooling

* docs: clean up flows terminology

* docs: fix flows product link grammar

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: LZylstra <11338479+LZylstra@users.noreply.github.com>

Author: 3 people

app/app.config.ts

@@ -37,7 +37,7 @@ export default defineAppConfig({
 				to: '/getting-started/overview',
 			},
 			{
-				label: 'Guides',
+				label: 'Guide',
 				children: [
 					{
 						label: 'Data Model',
@@ -55,7 +55,7 @@ export default defineAppConfig({
 						icon: 'directus-auth',
 					},
 					{
-						label: 'Connect',
+						label: 'APIs',
 						to: '/guides/connect/authentication',
 						icon: 'directus-connect',
 					},
@@ -65,7 +65,7 @@ export default defineAppConfig({
 						icon: 'directus-files',
 					},
 					{
-						label: 'Automate',
+						label: 'Flows',
 						to: '/guides/automate/flows',
 						icon: 'directus-automate',
 					},
@@ -107,7 +107,7 @@ export default defineAppConfig({
 				],
 			},
 			{
-				label: 'Manage',
+				label: 'Deploy',
 				children: [
 					{
 						label: 'Cloud',

app/components/content/ProductLink.vue

@@ -3,23 +3,28 @@ const props = defineProps<{
 	product: keyof typeof linkMap;
 }>();
 
-const name = computed(
-	() => props.product.charAt(0).toUpperCase() + props.product.slice(1),
-);
-
 const linkMap = {
 	'auth': '/guides/auth/tokens-cookies',
 	'automate': '/guides/automate/flows',
 	'content': '/guides/content/explore',
 	'connect': '/guides/connect/authentication',
 	'data-model': '/guides/data-model/collections',
-	'editor': '/guides/content/editor',
-	'explore': '/guides/content/explore',
 	'extensions': '/guides/extensions/overview',
 	'files': '/guides/files/upload',
 	'insights': '/guides/insights/overview',
 	'realtime': '/guides/realtime/subscriptions',
 } as const;
+
+const labelMap: Partial<Record<keyof typeof linkMap, string>> = {
+	'automate': 'Flows',
+	'connect': 'APIs',
+	'data-model': 'Data Model',
+};
+
+const name = computed(
+	() => labelMap[props.product]
+		?? props.product.charAt(0).toUpperCase() + props.product.slice(1),
+);
 </script>
 
 <template>

content/_partials/engine-studio-box.md

@@ -1,8 +1,8 @@
 ::shiny-grid{class="lg:grid-cols-2"}
   :::shiny-card
   ---
-  title: Data Engine
-  description: APIs and developer tools for your data.
+  title: APIs and Developer Tools
+  description: Build with REST, GraphQL, the SDK, realtime, auth, and Flows.
   color: purple
   ---
   :product-link{product="connect"} :product-link{product="realtime"} :product-link{product="auth"} :product-link{product="automate"}
@@ -11,9 +11,9 @@
   :::shiny-card
   ---
   title: Data Studio
-  description: A data web app your whole team will love.
+  description: A web app for your whole team to manage content, files, users, and dashboards.
   color: pink
   ---
-  :product-link{product="explore"} :product-link{product="editor"} :product-link{product="insights"} :product-link{product="files"}
+  :product-link{product="insights"} :product-link{product="files"}
   :::
 ::

content/community/2.contribution/2.documentation.md

@@ -22,7 +22,7 @@ We care about writing succinct, inclusive, and well-considered documentation. To
 
 For tutorials, we use the imperative mood instead of the gerund form. For example - "Build an Extension to Show Cat Pictures" instead of "Building an Extension to show cat pictures." 
 
-We end each title with technologies and product used, lowercasing the word 'with' before the tools. For example "Send SMS Messages with Twilio and Directus Automate."
+We end each title with technologies and product used, lowercasing the word 'with' before the tools. For example "Send SMS Messages with Twilio and Directus Flows."
 
 #### Contextualizing and Setting Goals
 

content/community/3.codebase/1.overview.md

@@ -6,7 +6,7 @@ navigation:
   title: Codebase
 ---
 
-The :icon{name="simple-icons:github"} [directus/directus](https://github.com/directus/directus) repository includes the Data Studio, Directus Connect, the JavaScript SDK, and a number of smaller packages used internally. All of these live in a single monorepo.
+The :icon{name="simple-icons:github"} [directus/directus](https://github.com/directus/directus) repository includes the Data Studio, the API server, the JavaScript SDK, and a number of smaller packages used internally. All of these live in a single monorepo.
 
 ## Data Studio
 

content/getting-started/1.overview.md

@@ -2,12 +2,12 @@
 stableId: 8d6c731d-b669-41e7-8549-3b641969fb4e
 title: Overview
 headline: Getting Started
-description: Learn about the Directus Data Engine and Studio, when to use it, and how it works.
+description: Learn what Directus is, when to use it, and how it works.
 navigation:
   title: Overview
 ---
 
-Directus is a backend for building your projects. Connect it to your database, asset storage, and external services, and immediately receive rich developer tooling (Data Engine) and a comprehensive web application (Data Studio) to work with your data. Granular access control means users can only see, interact with, and create the data their role allows.
+Directus is a backend for building your projects. Connect it to your database, asset storage, and external services, and immediately get a REST and GraphQL API, an SDK, realtime, auth, file management, automations, and a web application to work with your data. Granular access control means users can only see, interact with, and create the data their role allows.
 
 :partial{content="engine-studio-box"}
 

content/getting-started/7.create-an-automation.md

@@ -1,14 +1,14 @@
 ---
 stableId: 2f1467c4-ca73-4826-a674-f0e7b6a3afd9
-title: Create an Automation
-description: Get started using flows, triggers, operations and the data chain in Directus Automate.
+title: Create a Flow
+description: Get started using flows, triggers, operations, and the data chain in Directus.
 navigation:
-  title: Create an Automation
+  title: Create a Flow
 ---
 
 :video-embed{video-id="6e6965e7-13cc-4f86-b512-f567d66cfbe9"}
 
-This guide will cover custom event-driven data processing using Directus Automate.
+This guide will cover custom event-driven data processing using Flows.
 
 ## Before You Start
 

content/guides/01.data-model/1.collections.md

@@ -12,7 +12,7 @@ There are two types of collections: **user collections** and **system collection
 
 ## Creating Collections
 
-**User collections** are created directly in your database or via Directus. They describe your specific data models and configurations and can be queried via APIs created by :product-link{product="connect"} or via :product-link{product="explore"}.
+**User collections** are created directly in your database or via Directus. They describe your specific data models and configurations and can be queried via APIs created by :product-link{product="connect"} or browsed on the [collection page](/guides/content/explore).
 
 You can create collections from the Data Model settings in the Directus Data Studio, or using the [Collections API](/api/collections).
 
@@ -65,7 +65,7 @@ Once a collection is created, there are a number of configuration options availa
 
 ### Content Versioning
 
-Content versioning is used by :product-link{product="editor"} and allows teams to create and manage different versions of their content. There are several reasons to use content versioning, including drafting content without publishing it, and more ways to collaborate with others.
+Content versioning is used on the [item page](/guides/content/editor) and allows teams to create and manage different versions of their content. There are several reasons to use content versioning, including drafting content without publishing it, and more ways to collaborate with others.
 
 This feature can be enabled for specific collections, and will be available for all items. Once enabled, item versions can be created, and later have some or all fields promoted to the main version, typically used for publishing.
 
@@ -75,7 +75,7 @@ Read the content versioning user guide.
 
 ### Live Preview
 
-Live preview is used by :product-link{product="editor"} and allows for your application to be shown in a pane next to your content, which can be used for previewing content before publishing.
+Live preview is used on the [item page](/guides/content/editor) and allows for your application to be shown in a pane next to your content, which can be used for previewing content before publishing.
 
 You can use item field values to construct the URL used by the live preview, including unique identifiers and content version, allowing for previewing content versions before promoting them to the main version.
 
@@ -109,7 +109,7 @@ Once configured, click :icon{name="material-symbols:sort" title="Sort Button"} i
 
 ### Duplication
 
-The **Save as Copy** option in :product-link{product="editor"} offers a way to effectively duplicate the current item. Duplication settings define which field values will be copied.
+The **Save as Copy** option on the [item page](/guides/content/editor) offers a way to effectively duplicate the current item. Duplication settings define which field values will be copied.
 
 ::callout{icon="material-symbols:info-outline"}
 

content/guides/01.data-model/2.fields.md

@@ -30,7 +30,7 @@ When creating a new field, you must first select an [interface](/guides/data-mod
 
 ![Field creation form showing datetime field](/img/426fb648-1e88-46e4-92f1-af76f3254d25.webp)
 
-The **interface** describes how users will create and edit data, as well as how it is displayed in :product-link{product="editor"}. There are many kinds of built-in interface, such as a text input, date selector, map, and a set of relationship interfaces. More interfaces can be built as [extensions](/guides/extensions/overview).
+The **interface** describes how users will create and edit data, as well as how it is displayed on the [item page](/guides/content/editor). There are many kinds of built-in interface, such as a text input, date selector, map, and a set of relationship interfaces. More interfaces can be built as [extensions](/guides/extensions/overview).
 
 The **key** is the unique name for a field within a collection. This value is used in both the Data Studio and via API. Within the Data Studio, the key is parsed through our title formatter to improve readability.
 

content/guides/01.data-model/3.interfaces.md

@@ -4,7 +4,7 @@ title: Interfaces
 description: Manage your data effectively with Directus fields. Discover various field types, interfaces, validations, and relationships to perfectly suit your data modeling needs.
 ---
 
-Interfaces are how users interact with fields in :product-link{product="editor"}. Each interface supports specific data types and configurations.
+Interfaces are how users interact with fields on the [item page](/guides/content/editor). Each interface supports specific data types and configurations.
 
 ## Text & Numbers