Merge branch 'current' into patch-4

.github/pull_request_template.md

@@ -1,26 +1,23 @@
 ## What are you changing in this pull request and why?
 <!---
-Describe your changes and why you're making them. If linked to an open
+Describe your changes and why you're making them. If related to an open 
 issue or a pull request on dbt Core, then link to them here! 
 
 To learn more about the writing conventions used in the dbt Labs docs, see the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md).
 -->
 
 ## Checklist
 <!--
-Uncomment if you're publishing docs for a prerelease version of dbt (delete if not applicable):
+Uncomment when publishing docs for a prerelease version of dbt:
 - [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
 - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
 -->
 - [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines.
 - [ ] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
 - [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
 
-Adding new pages (delete if not applicable):
-- [ ] Add page to `website/sidebars.js`
-- [ ] Provide a unique filename for the new page
-
-Removing or renaming existing pages (delete if not applicable):
-- [ ] Remove page from `website/sidebars.js`
-- [ ] Add an entry `website/static/_redirects`
-- [ ] Run link testing locally with `npm run build` to update the links that point to the deleted page
+Adding or removing pages (delete if not applicable):
+- [ ] Add/remove page in `website/sidebars.js`
+- [ ] Provide a unique filename for new pages
+- [ ] Add an entry for deleted pages in `website/static/_redirects`
+- [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages

website/blog/authors.yml

@@ -1,6 +1,6 @@
 amy_chen:
   image_url: /img/blog/authors/achen.png
-  job_title: Product Partnerships Manager
+  job_title: Product Ecosystem Manager
   links:
     - icon: fa-linkedin
       url: https://www.linkedin.com/in/yuanamychen/

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-1-intro.md

@@ -2,6 +2,8 @@
 title: "Intro to MetricFlow"
 description: Getting started with the dbt and MetricFlow
 hoverSnippet: Learn how to get started with the dbt and MetricFlow
+pagination_next: "best-practices/how-we-build-our-metrics/semantic-layer-2-setup"
+pagination_prev: null
 ---
 
 Flying cars, hoverboards, and true self-service analytics: this is the future we were promised. The first two might still be a few years out, but real self-service analytics is here today. With dbt Cloud's Semantic Layer, you can resolve the tension between accuracy and flexibility that has hampered analytics tools for years, empowering everybody in your organization to explore a shared reality of metrics. Best of all for analytics engineers, building with these new tools will significantly [DRY](https://docs.getdbt.com/terms/dry) up and simplify your codebase. As you'll see, the deep interaction between your dbt models and the Semantic Layer make your dbt project the ideal place to craft your metrics.

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-2-setup.md

@@ -2,6 +2,7 @@
 title: "Set up MetricFlow"
 description: Getting started with the dbt and MetricFlow
 hoverSnippet: Learn how to get started with the dbt and MetricFlow
+pagination_next: "best-practices/how-we-build-our-metrics/semantic-layer-3-build-semantic-models"
 ---
 
 ## Getting started
@@ -13,9 +14,23 @@ git clone [email protected]:dbt-labs/jaffle-sl-template.git
 cd path/to/project
 ```
 
-Next, before you start writing code, you need to install MetricFlow as an extension of a dbt adapter from PyPI  (dbt Core users only). The MetricFlow is compatible with Python versions 3.8 through 3.11.
+Next, before you start writing code, you need to install MetricFlow:
 
-We'll use pip to install MetricFlow and our dbt adapter:
+<Tabs>
+
+<TabItem value="cloud" label="dbt Cloud">
+
+- [dbt Cloud CLI](/docs/cloud/cloud-cli-installation) &mdash; MetricFlow commands are embedded in the dbt Cloud CLI. You can immediately run them once you install the dbt Cloud CLI. Using dbt Cloud means you won't need to manage versioning — your dbt Cloud account will automatically manage the versioning.
+
+- [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud) &mdash; You can create metrics using MetricFlow in the dbt Cloud IDE. However, support for running MetricFlow commands in the IDE will be available soon.
+
+</TabItem>
+
+<TabItem value="core" label="dbt Core">
+
+- Download MetricFlow as an extension of a dbt adapter from PyPI  (dbt Core users only). The MetricFlow is compatible with Python versions 3.8 through 3.11. 
+  - **Note**: You'll need to manage versioning between dbt Core, your adapter, and MetricFlow.
+- We'll use pip to install MetricFlow and our dbt adapter:
 
 ```shell
 # activate a virtual environment for your project,
@@ -27,13 +42,16 @@ python -m pip install "dbt-metricflow[adapter name]"
 # e.g. python -m pip install "dbt-metricflow[snowflake]"
 ```
 
-Lastly, to get to the pre-Semantic Layer starting state, checkout the `start-here` branch.
+</TabItem>
+</Tabs>
+
+- Now that you're ready to use MetricFlow, get to the pre-Semantic Layer starting state by checking out the `start-here` branch:
 
 ```shell
 git checkout start-here
 ```
 
-For more information, refer to the [MetricFlow commands](/docs/build/metricflow-commands) or a [quickstart](/guides) to get more familiar with setting up a dbt project.
+For more information, refer to the [MetricFlow commands](/docs/build/metricflow-commands) or the [quickstart guides](/guides) to get more familiar with setting up a dbt project.
 
 ## Basic commands
 

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-3-build-semantic-models.md

@@ -2,6 +2,7 @@
 title: "Building semantic models"
 description: Getting started with the dbt and MetricFlow
 hoverSnippet: Learn how to get started with the dbt and MetricFlow
+pagination_next: "best-practices/how-we-build-our-metrics/semantic-layer-4-build-metrics"
 ---
 
 ## How to build a semantic model

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-4-build-metrics.md

@@ -2,6 +2,7 @@
 title: "Building metrics"
 description: Getting started with the dbt and MetricFlow
 hoverSnippet: Learn how to get started with the dbt and MetricFlow
+pagination_next: "best-practices/how-we-build-our-metrics/semantic-layer-5-refactor-a-mart"
 ---
 
 ## How to build metrics

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-5-refactor-a-mart.md

@@ -2,6 +2,7 @@
 title: "Refactor an existing mart"
 description: Getting started with the dbt and MetricFlow
 hoverSnippet: Learn how to get started with the dbt and MetricFlow
+pagination_next: "best-practices/how-we-build-our-metrics/semantic-layer-6-advanced-metrics"
 ---
 
 ## A new approach

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-6-advanced-metrics.md

@@ -2,6 +2,7 @@
 title: "More advanced metrics"
 description: Getting started with the dbt and MetricFlow
 hoverSnippet: Learn how to get started with the dbt and MetricFlow
+pagination_next: "best-practices/how-we-build-our-metrics/semantic-layer-7-conclusion"
 ---
 
 ## More advanced metric types

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-7-conclusion.md

@@ -2,6 +2,7 @@
 title: "Best practices"
 description: Getting started with the dbt and MetricFlow
 hoverSnippet: Learn how to get started with the dbt and MetricFlow
+pagination_next: null
 ---
 
 ## Putting it all together

website/docs/best-practices/how-we-mesh/mesh-1-intro.md

@@ -12,7 +12,7 @@ Regardless of your organization's size and complexity, dbt should empower data t
 
 dbt Mesh is not a single product: it is a pattern enabled by a convergence of several features in dbt:
 
-- **[Cross-project references](/docs/collaborate/govern/project-dependencies#how-to-use-ref)** - this is the foundational feature that enables the multi-project deployments. `{{ ref() }}`s now work across dbt Cloud projects on Enterprise plans.
+- **[Cross-project references](/docs/collaborate/govern/project-dependencies#how-to-write-cross-project-ref)** - this is the foundational feature that enables the multi-project deployments. `{{ ref() }}`s now work across dbt Cloud projects on Enterprise plans.
 - **[dbt Explorer](/docs/collaborate/explore-projects)** - dbt Cloud's metadata-powered documentation platform, complete with full, cross-project lineage.
 - **Governance** - dbt's new governance features allow you to manage access to your dbt models both within and across projects.
   - **[Groups](/docs/collaborate/govern/model-access#groups)** - groups allow you to assign models to subsets within a project.
@@ -32,6 +32,8 @@ dbt Cloud is designed to coordinate the features above and simplify the complexi
 
 If you're just starting your dbt journey, don't worry about building a multi-project architecture right away. You can _incrementally_ adopt the features in this guide as you scale. The collection of features work effectively as independent tools. Familiarizing yourself with the tooling and features that make up a multi-project architecture, and how they can apply to your organization will help you make better decisions as you grow.
 
+For additional information, refer to the [dbt Mesh FAQs](/best-practices/how-we-mesh/mesh-4-faqs).
+
 ## Learning goals
 
 - Understand the **purpose and tradeoffs** of building a multi-project architecture.

website/docs/best-practices/how-we-mesh/mesh-2-structures.md

@@ -20,7 +20,7 @@ At a high level, you’ll need to decide:
 
 ### Cycle detection
 
-Like resource dependencies, project dependencies are acyclic, meaning they only move in one direction. This prevents `ref` cycles (or loops), which lead to issues with your data workflows. For example, if project B depends on project A, a new model in project A could not import and use a public model from project B. Refer to [Project dependencies](/docs/collaborate/govern/project-dependencies#how-to-use-ref) for more information. 
+Like resource dependencies, project dependencies are acyclic, meaning they only move in one direction. This prevents `ref` cycles (or loops), which lead to issues with your data workflows. For example, if project B depends on project A, a new model in project A could not import and use a public model from project B. Refer to [Project dependencies](/docs/collaborate/govern/project-dependencies#how-to-write-cross-project-ref) for more information. 
 
 ## Define your project interfaces by splitting your DAG