fix docs-engine links

adamschwartz · adamschwartz · commit 302d8f19ee66 · 2020-10-10T10:12:26.000-04:00
diff --git a/products/docs-engine/src/content/contributing/content-framework.md b/products/docs-engine/src/content/contributing/content-framework.md
@@ -56,10 +56,10 @@ The first Cloudflare product to adopt this system was the Cloudflare Workers doc
 
 Within Cloudflare Workers, the division is as as follows:
 
-1. **Tutorials** – The [Tutorials](/tutorials) section.
-2. **How-to guides** – Though a work-in-progress¹, [Examples](/examples) and [Starters](/starters).
-3. **Technical reference** – Three² components: [Platform](/platform), [Runtime APIs](/runtime-apis), and [CLI (Wrangler)](/cli-wrangler).
-4. **Explanation** – The [Learning](/learning) section.
+1. **Tutorials** – The [Tutorials](https://developers.cloudflare.com/workers/tutorials) section.
+2. **How-to guides** – Though a work-in-progress¹, [Examples](https://developers.cloudflare.com/workers/examples) and [Starters](https://developers.cloudflare.com/workers/starters).
+3. **Technical reference** – Three² components: [Platform](https://developers.cloudflare.com/workers/platform), [Runtime APIs](https://developers.cloudflare.com/workers/runtime-apis), and [CLI (Wrangler)](https://developers.cloudflare.com/workers/cli-wrangler).
+4. **Explanation** – The [Learning](https://developers.cloudflare.com/workers/learning) section.
 
 ¹ _[Examples](/examples) certainly do “show how to solve a specific problem”, but as currently written, they don’t always provide a clear “series of steps”, similar to a recipe in a cookbook. This is something we’d like to improve over time._
 
@@ -81,7 +81,7 @@ Cloudflare documentation should be practical and approachable.
 
 ### Writing technical reference
 
-When writing documentation as part of a technical reference (e.g. [runtime API](/runtime-apis) doc), follow these additional guidelines ([from Divio](https://documentation.divio.com/reference/#reference)):
+When writing documentation as part of a technical reference (e.g. [runtime API](https://developers.cloudflare.com/workers/runtime-apis) doc), follow these additional guidelines ([from Divio](https://documentation.divio.com/reference/#reference)):
 
 - **Structure the documentation around the codebase.** When documenting a set of APIs, for example, name and organize the files to match the codebase’s naming and folder structure. This helps ensure consistency when communicating with users, who may see and interact with codebase, and helps maintainers see where documentation is missing or needs to be updated.
 
diff --git a/products/docs-engine/src/content/faq.md b/products/docs-engine/src/content/faq.md
@@ -9,14 +9,14 @@ order: 6
 
 ## Why a Docs Engine?
 
-__tl:dr;__ You write good [Markdown (MDX)](/markdown), and the rest is taken care of.
+__tl:dr;__ You write good [Markdown (MDX)](/reference/markdown), and the rest is taken care of.
 
 __Details:__ Cloudflare has a large number of teams shipping product updates often. Most of these products have [their own documentation](https://developers.cloudflare.com/docs/). Over time we’ve found that it’s especially difficult to balance two important goals:
 
 1. Content is easily managed by the product team that owns it.
 2. Docs are consistent across products, providing the _best experience for our customers_, who commonly use more than one Cloudflare product together.
 
-The Docs Engine strives to solve these problems by providing smart defaults with minimal [configuration](/site-configuration) and a wide variety of [composable MDX components](/markdown).
+The Docs Engine strives to solve these problems by providing smart defaults with minimal [configuration](/reference/configuration) and a wide variety of [composable MDX components](/reference/markdown).
 
 ## How does the main navigation work?
 
diff --git a/products/docs-engine/src/content/how-it-works.md b/products/docs-engine/src/content/how-it-works.md
@@ -10,7 +10,7 @@ __Note for Cloudflare employees:__ The details of this process are still being w
 
 </Aside>
 
-In short, docs sites built with the Cloudflare Docs Engine are [Gatsby](https://www.gatsbyjs.com) sites with a bunch of [custom MDX components](/markdown) and a shell UI you that’s consistent across products, all deployed as a [Workers Sites project](https://workers.cloudflare.com/sites) via the [Wrangler GitHub Action](https://github.com/cloudflare/wrangler-action).
+In short, docs sites built with the Cloudflare Docs Engine are [Gatsby](https://www.gatsbyjs.com) sites with a bunch of [custom MDX components](/reference/markdown) and a shell UI you that’s consistent across products, all deployed as a [Workers Sites project](https://workers.cloudflare.com/sites) via the [Wrangler GitHub Action](https://github.com/cloudflare/wrangler-action).
 
 --------------------------------
 
diff --git a/products/docs-engine/src/content/how-to-guides/migrate-a-product.md b/products/docs-engine/src/content/how-to-guides/migrate-a-product.md
@@ -93,10 +93,10 @@ At this point, you can make changes to the Markdown files inside the contect dir
 
 In terms of improving/updating the content itself, there are a number of great resources available to help:
 
-- __[Content framework](/contributing/content-framework)__ – Cloudflare’s new docs sites (e.g. [Workers](https://developers.cloudflare.com/workers/)) are starting to adhere to a content framework which may be helpful when thinking about how to structure your [pages](/reference/pages) (folders and Markdown files) and create logical [side navigation](/reference/sidebar).
+- __[Content framework](/contributing/content-framework)__ – Cloudflare’s new docs sites (e.g. [Workers](https://developers.cloudflare.com/workers/)) are starting to adhere to a content framework which may be helpful when thinking about how to structure your [pages](/reference/pages) (folders and Markdown files) and create logical [side navigation](reference/pages#url-paths).
 
 
-- __[Markdown (MDX) built-in components](/reference/markdown)__ – Migrating to the new Docs Engine means you can take advantage of all of its powerful [built-in components](/reference/markdown). Add an [aside](/reference/markdown), [display code beautifully](/reference/markdown/code-block-examples), [embed a video](/reference/markdown), add a buttons, definition list, and [so much more](/reference/markdown).
+- __[Markdown (MDX) built-in components](/reference/markdown)__ – Migrating to the new Docs Engine means you can take advantage of all of its powerful [built-in components](/reference/markdown). Add an [aside](/reference/markdown#asides), [display code beautifully](reference/markdown#code-blocks), [embed a video](/reference/markdown#youtube), add a buttons, definition list, and [so much more](/reference/markdown).
 
 
 - [__Workers docs site__ example](https://developers.cloudflare.com/workers) – You can also take a look at the [Workers content](https://github.com/cloudflare/cloudflare-docs/tree/4fd3a4af9507b20bb23fea4d7c4f4cd349c0f463/products/workers/src/content) for an example of a well-structured docs site.
diff --git a/products/docs-engine/src/content/index.md b/products/docs-engine/src/content/index.md
@@ -10,7 +10,7 @@ order: 0
 
 Documentation for the __Docs Engine__ which powers Cloudflare’s developer docs.
 
-The engine is built with [Gatsby](https://www.gatsbyjs.com/), and makes generous use of custom [MDX components](/markdown).
+The engine is built with [Gatsby](https://www.gatsbyjs.com/), and makes generous use of custom [MDX components](/reference/markdown).
 
 It’s __open-source__ and [available on GitHub](https://github.com/cloudflare/cloudflare-docs-engine).
 
diff --git a/products/docs-engine/src/content/reference/markdown.md b/products/docs-engine/src/content/reference/markdown.md
@@ -21,9 +21,9 @@ Visit [example.com](https://example.com).
 ```markdown
 Visit [example.com](https://example.com).
 
-View the [Tutorials](/tutorials) tutorials.
+View the [How it Works](/how-it-works) page.
 
-Learn how [V8:Isolates power Workers](/how-workers-works#isolates).
+Learn how to use [`<Asides/>`](/reference/markdown#asides).
 ```
 
 - __Internal links__ will use [Gatsby’s `<Link/>` component](https://www.gatsbyjs.org/docs/gatsby-link/), which means they will be routed through `@reach/router` using `pushState`.
@@ -32,14 +32,14 @@ Learn how [V8:Isolates power Workers](/how-workers-works#isolates).
 If you need to take advantage of Gatsby’s routing but you want control over the presentation of the link yourself, you can use `<Link/>` directly.
 
 ```markdown
-<Link to="/examples" className="Button Button-is-secondary">
-  View examples
+<Link to="/how-it-works" className="Button Button-is-secondary">
+  How it Works
 </Link>
 ```
 
 <Example>
-<Link to="/examples" className="Button Button-is-secondary">
-  View examples
+<Link to="/how-it-works" className="Button Button-is-secondary">
+  How it Works
 </Link>
 </Example>
 
