From ad38164c063a2cea1894848e41865f74815c44a6 Mon Sep 17 00:00:00 2001 From: Jason Ganz Date: Tue, 7 Nov 2023 10:35:50 -0500 Subject: [PATCH 1/6] update wording in intro --- .../best-practices/how-we-mesh/mesh-1-intro.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md index ba1660a8d82..567fc18b5e7 100644 --- a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md +++ b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md @@ -6,25 +6,25 @@ hoverSnippet: Learn how to get started with dbt Mesh ## What is dbt Mesh? -Organizations of all sizes rely upon dbt to manage their data transformations, from small startups to large enterprises. At scale, it can be challenging to coordinate all the organizational and technical requirements demanded by your stakeholders within the scope of a single dbt project. To date, there also hasn't been a first-class way to effectively manage the dependencies, governance, and workflows between multiple dbt projects. +Organizations of all sizes rely upon dbt to manage their data transformations, from small startups to large enterprises. At scale, it can be challenging to coordinate all the organizational and technical requirements demanded by your stakeholders within the scope of a single dbt project. To date, there also hasn't been a first-class way to effectively manage the dependencies, governance, and workflows between multiple dbt projects. -Regardless of your organization's size and complexity, dbt should empower data teams to work independently and collaboratively; sharing data, code, and best practices without sacrificing security or autonomy. dbt Mesh provides the tooling for teams to finally achieve this. +That's where dbt Mesh comes in - empowering data teams to work independently and collaboratively; sharing data, code, and best practices without sacrificing security or autonomy. This guide will walk you through the concepts and implementation details needed to get started. 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#usage)** - 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. - - **[Access](/docs/collaborate/govern/model-access#access-modifiers)** - access configs allow you to control who can reference models. -- **[Model Versions](/docs/collaborate/govern/model-versions)** - when coordinating across projects and teams, we recommend treating your data models as stable APIs. Model versioning is the mechanism to allow graceful adoption and deprecation of models as they evolve. -- **[Model Contracts](/docs/collaborate/govern/model-contracts)** - data contracts set explicit expectations on the shape of the data to ensure data changes upstream of dbt or within a project's logic don't break downstream consumers' data products. + - **[Groups](/docs/build/groups)** - groups allow you to gather together nodes in your dbt DAG that are logically connected (such as functional area) and assign an owner to the group. + - **[Access](/docs/collaborate/govern/model-access)** - access configs allow you to control who can reference models. + - **[Model Versions](/docs/collaborate/govern/model-versions)** - When coordinating across projects and teams, we recommend treating your data models as stable APIs. Model versioning is the mechanism to allow graceful adoption and deprecation of models as they evolve. + - **[Model Contracts](/docs/collaborate/govern/model-contracts)** - data contracts set explicit expectations on the shape of the data to ensure data changes upstream of dbt or within a project's logic don't break downstream comsumers' data products. ## Who is dbt Mesh for? -The multi-project architecture helps organizations with mature, complex transformation workflows in dbt increase the flexibility and performance of their dbt projects. If you're already using dbt and your project has started to experience any of the following, you're likely ready to start exploring this paradigm: +The multi-project architecture is for organizations with mature, complex transformation workflows in dbt who want to increase the flexibilty and performance of their dbt projects. If you're already using dbt and your project has started to experience any of the following, you're likely ready to start exploring this paradigm: -- The **number of models** in your project is degrading performance and slowing down development. +- **The number of models** in your project is degrading performance and slowing down development. - Teams have developed **separate workflows** and need to decouple development from each other. - **Security and governance** requirements are increasing and would benefit from increased isolation. From 81c51822677848069ec56b05f340bd1dcea946a0 Mon Sep 17 00:00:00 2001 From: Jason Ganz Date: Tue, 7 Nov 2023 10:46:05 -0500 Subject: [PATCH 2/6] restore unwanted changes --- .../how-we-mesh/mesh-1-intro.md | 22 ++++++++++--------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md index 567fc18b5e7..9f4ee6b0e14 100644 --- a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md +++ b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md @@ -6,25 +6,27 @@ hoverSnippet: Learn how to get started with dbt Mesh ## What is dbt Mesh? -Organizations of all sizes rely upon dbt to manage their data transformations, from small startups to large enterprises. At scale, it can be challenging to coordinate all the organizational and technical requirements demanded by your stakeholders within the scope of a single dbt project. To date, there also hasn't been a first-class way to effectively manage the dependencies, governance, and workflows between multiple dbt projects. +Organizations of all sizes rely upon dbt to manage their data transformations, from small startups to large enterprises. At scale, it can be challenging to coordinate all the organizational and technical requirements demanded by your stakeholders within the scope of a single dbt project. -That's where dbt Mesh comes in - empowering data teams to work independently and collaboratively; sharing data, code, and best practices without sacrificing security or autonomy. This guide will walk you through the concepts and implementation details needed to get started. +To date, there also hasn't been a first-class way to effectively manage the dependencies, governance, and workflows between multiple dbt projects. -dbt Mesh is not a single product: it is a pattern enabled by a convergence of several features in dbt: +That's where **dbt Mesh** comes in - empowering data teams to work *independently and collaboratively*; sharing data, code, and best practices without sacrificing security or autonomy. -- **[Cross-project references](/docs/collaborate/govern/project-dependencies#usage)** - this is the foundational feature that enables the multi-project deployments. `{{ ref() }}`s now work across dbt Cloud projects on Enterprise plans. +This guide will walk you through the concepts and implementation details needed to get started. 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. - **[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/build/groups)** - groups allow you to gather together nodes in your dbt DAG that are logically connected (such as functional area) and assign an owner to the group. - - **[Access](/docs/collaborate/govern/model-access)** - access configs allow you to control who can reference models. - - **[Model Versions](/docs/collaborate/govern/model-versions)** - When coordinating across projects and teams, we recommend treating your data models as stable APIs. Model versioning is the mechanism to allow graceful adoption and deprecation of models as they evolve. - - **[Model Contracts](/docs/collaborate/govern/model-contracts)** - data contracts set explicit expectations on the shape of the data to ensure data changes upstream of dbt or within a project's logic don't break downstream comsumers' data products. + - **[Groups](/docs/collaborate/govern/model-access#groups)** - groups allow you to gather together nodes in your dbt DAG that are logically connected (such as functional area) and assign an owner to the group. + - **[Access](/docs/collaborate/govern/model-access#access-modifiers)** - access configs allow you to control who can reference models. + - **[Model Versions](/docs/collaborate/govern/model-versions)** - when coordinating across projects and teams, we recommend treating your data models as stable APIs. Model versioning is the mechanism to allow graceful adoption and deprecation of models as they evolve. + - **[Model Contracts](/docs/collaborate/govern/model-contracts)** - data contracts set explicit expectations on the shape of the data to ensure data changes upstream of dbt or within a project's logic don't break downstream consumers' data products. ## Who is dbt Mesh for? -The multi-project architecture is for organizations with mature, complex transformation workflows in dbt who want to increase the flexibilty and performance of their dbt projects. If you're already using dbt and your project has started to experience any of the following, you're likely ready to start exploring this paradigm: +The multi-project architecture helps organizations with mature, complex transformation workflows in dbt increase the flexibility and performance of their dbt projects. If you're already using dbt and your project has started to experience any of the following, you're likely ready to start exploring this paradigm: -- **The number of models** in your project is degrading performance and slowing down development. +- The **number of models** of models** in your project is degrading performance and slowing down development. - Teams have developed **separate workflows** and need to decouple development from each other. - **Security and governance** requirements are increasing and would benefit from increased isolation. From 88b7e3a0738c77e0718357432bf731c5add5cf0d Mon Sep 17 00:00:00 2001 From: Jason Ganz Date: Tue, 7 Nov 2023 10:48:47 -0500 Subject: [PATCH 3/6] update wording --- .../docs/guides/best-practices/how-we-mesh/mesh-1-intro.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md index 9f4ee6b0e14..7719b282a8a 100644 --- a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md +++ b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md @@ -17,7 +17,7 @@ This guide will walk you through the concepts and implementation details needed - **[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. - **[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 gather together nodes in your dbt DAG that are logically connected (such as functional area) and assign an owner to the group. + - **[Groups](/docs/collaborate/govern/model-access#groups)** - groups allow you to gather together nodes in your dbt DAG that are logically connected (such as by functional area) and assign an owner to the group. - **[Access](/docs/collaborate/govern/model-access#access-modifiers)** - access configs allow you to control who can reference models. - **[Model Versions](/docs/collaborate/govern/model-versions)** - when coordinating across projects and teams, we recommend treating your data models as stable APIs. Model versioning is the mechanism to allow graceful adoption and deprecation of models as they evolve. - **[Model Contracts](/docs/collaborate/govern/model-contracts)** - data contracts set explicit expectations on the shape of the data to ensure data changes upstream of dbt or within a project's logic don't break downstream consumers' data products. @@ -26,7 +26,7 @@ This guide will walk you through the concepts and implementation details needed The multi-project architecture helps organizations with mature, complex transformation workflows in dbt increase the flexibility and performance of their dbt projects. If you're already using dbt and your project has started to experience any of the following, you're likely ready to start exploring this paradigm: -- The **number of models** of models** in your project is degrading performance and slowing down development. +- The **number of models** in your project is degrading performance and slowing down development. - Teams have developed **separate workflows** and need to decouple development from each other. - **Security and governance** requirements are increasing and would benefit from increased isolation. From c590ec0f725628122e242f93d061aefbf256cc36 Mon Sep 17 00:00:00 2001 From: Jason Ganz Date: Tue, 7 Nov 2023 10:58:41 -0500 Subject: [PATCH 4/6] update wording --- website/docs/collaborate/govern/model-access | 0 .../docs/guides/best-practices/how-we-mesh/mesh-1-intro.md | 4 ++-- 2 files changed, 2 insertions(+), 2 deletions(-) create mode 100644 website/docs/collaborate/govern/model-access diff --git a/website/docs/collaborate/govern/model-access b/website/docs/collaborate/govern/model-access new file mode 100644 index 00000000000..e69de29bb2d diff --git a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md index 7719b282a8a..33f1b9520d0 100644 --- a/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md +++ b/website/docs/guides/best-practices/how-we-mesh/mesh-1-intro.md @@ -12,11 +12,11 @@ To date, there also hasn't been a first-class way to effectively manage the depe That's where **dbt Mesh** comes in - empowering data teams to work *independently and collaboratively*; sharing data, code, and best practices without sacrificing security or autonomy. -This guide will walk you through the concepts and implementation details needed to get started. dbt Mesh is not a single product: it is a pattern enabled by a convergence of several features in dbt: +This guide will walk you through the concepts and implementation details needed to get started. 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. - **[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. +- **Governance** - dbt's 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 gather together nodes in your dbt DAG that are logically connected (such as by functional area) and assign an owner to the group. - **[Access](/docs/collaborate/govern/model-access#access-modifiers)** - access configs allow you to control who can reference models. - **[Model Versions](/docs/collaborate/govern/model-versions)** - when coordinating across projects and teams, we recommend treating your data models as stable APIs. Model versioning is the mechanism to allow graceful adoption and deprecation of models as they evolve. From d812d2489045245d9197090664974f9ae53e7b5b Mon Sep 17 00:00:00 2001 From: Jason Ganz Date: Tue, 7 Nov 2023 11:00:56 -0500 Subject: [PATCH 5/6] Delete website/docs/collaborate/govern/model-access accidental add --- website/docs/collaborate/govern/model-access | 0 1 file changed, 0 insertions(+), 0 deletions(-) delete mode 100644 website/docs/collaborate/govern/model-access diff --git a/website/docs/collaborate/govern/model-access b/website/docs/collaborate/govern/model-access deleted file mode 100644 index e69de29bb2d..00000000000 From 4d8c2f244db3417017b2a02356c921652452a3e0 Mon Sep 17 00:00:00 2001 From: Jason Ganz Date: Mon, 13 Nov 2023 16:00:40 -0500 Subject: [PATCH 6/6] Update website/docs/best-practices/how-we-mesh/mesh-1-intro.md Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/best-practices/how-we-mesh/mesh-1-intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/best-practices/how-we-mesh/mesh-1-intro.md b/website/docs/best-practices/how-we-mesh/mesh-1-intro.md index 33f1b9520d0..186383b91c5 100644 --- a/website/docs/best-practices/how-we-mesh/mesh-1-intro.md +++ b/website/docs/best-practices/how-we-mesh/mesh-1-intro.md @@ -17,7 +17,7 @@ This guide will walk you through the concepts and implementation details needed - **[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. - **[dbt Explorer](/docs/collaborate/explore-projects)** - dbt Cloud's metadata-powered documentation platform, complete with full, cross-project lineage. - **Governance** - dbt's 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 gather together nodes in your dbt DAG that are logically connected (such as by functional area) and assign an owner to the group. + - **[Groups](/docs/collaborate/govern/model-access#groups)** - With groups, you can organize nodes in your dbt DAG that share a logical connection (for example, by functional area) and assign an owner to the entire group. - **[Access](/docs/collaborate/govern/model-access#access-modifiers)** - access configs allow you to control who can reference models. - **[Model Versions](/docs/collaborate/govern/model-versions)** - when coordinating across projects and teams, we recommend treating your data models as stable APIs. Model versioning is the mechanism to allow graceful adoption and deprecation of models as they evolve. - **[Model Contracts](/docs/collaborate/govern/model-contracts)** - data contracts set explicit expectations on the shape of the data to ensure data changes upstream of dbt or within a project's logic don't break downstream consumers' data products.