diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md
index 52864f98a0e..5a7d9f4bb13 100644
--- a/website/docs/docs/cloud/cloud-cli-installation.md
+++ b/website/docs/docs/cloud/cloud-cli-installation.md
@@ -10,11 +10,11 @@ dbt Cloud natively supports developing using a command line (CLI), empowering te
dbt commands are run against dbt Cloud's infrastructure and benefit from:
-* Secure credential storage in the dbt Cloud platform.
-* [Automatic deferral](/docs/cloud/about-cloud-develop-defer) of build artifacts to your Cloud project's production environment.
-* Speedier, lower-cost builds.
-* Support for dbt Mesh ([cross-project `ref`](/docs/collaborate/govern/project-dependencies)),
-* Significant platform improvements, to be released over the coming months.
+* Secure credential storage in the dbt Cloud platform
+* [Automatic deferral](/docs/cloud/about-cloud-develop-defer) of build artifacts to your Cloud project's production environment
+* Speedier, lower-cost builds
+* Support for dbt Mesh ([cross-project `ref`](/docs/collaborate/govern/project-dependencies))
+* Significant platform improvements, to be released over the coming months
diff --git a/website/docs/docs/collaborate/explore-projects.md b/website/docs/docs/collaborate/explore-projects.md
index 400c9666c86..0f9f4c6f899 100644
--- a/website/docs/docs/collaborate/explore-projects.md
+++ b/website/docs/docs/collaborate/explore-projects.md
@@ -6,13 +6,9 @@ pagination_next: "docs/collaborate/model-performance"
pagination_prev: null
---
-With dbt Explorer, you can view your project's [resources](/docs/build/projects) (such as models, tests, and metrics) and their lineage to gain a better understanding of its latest production state. Navigate and manage your projects within dbt Cloud to help you and other data developers, analysts, and consumers discover and leverage your dbt resources.
-
-:::tip Public preview
+# Explore your dbt projects
-Try dbt Explorer! It's available in [Public Preview](/docs/dbt-versions/product-lifecycles#dbt-cloud) as of October 17, 2023 for dbt Cloud customers. More updates coming soon.
-
-:::
+With dbt Explorer, you can view your project's [resources](/docs/build/projects) (such as models, tests, and metrics) and their lineage to gain a better understanding of its latest production state. Navigate and manage your projects within dbt Cloud to help you and other data developers, analysts, and consumers discover and leverage your dbt resources.
## Prerequisites
@@ -51,75 +47,107 @@ By default, dbt Explorer shows the project's [applied state](/docs/dbt-cloud-api
To explore the lineage graphs of tests and macros, view [their resource details pages](#view-resource-details). By default, dbt Explorer excludes these resources from the full lineage graph unless a search query returns them as results.
-To interact with the full lineage graph, you can:
+
- Hover over any item in the graph to display the resource’s name and type.
- Zoom in and out on the graph by mouse-scrolling.
- Grab and move the graph and the nodes.
- Right click on a node (context menu) to:
- - Refocus on the node, including its parent and child nodes
- - Refocus on the node and its children only
- - Refocus on the node and it parents only
+ - Refocus on the node, including its upstream and downstream nodes
+ - Refocus on the node and its downstream nodes only
+ - Refocus on the node and it upstream nodes only
- View the node's [resource details](#view-resource-details) page
-
- Select a resource to highlight its relationship with other resources in your project. A panel opens on the graph’s right-hand side that displays a high-level summary of the resource’s details. The side panel includes a **General** tab for information like description, materialized type, and other details.
- Click the Share icon in the side panel to copy the graph’s link to your clipboard.
- Click the View Resource icon in the side panel to [view the resource details](#view-resource-details).
-- [Search and select specific resources](#search-resources) or a subset of the DAG using [selectors](/reference/node-selection/methods) and [graph operators](/reference/node-selection/graph-operators). This can help you narrow the focus on the resources that interest you. For example:
- - `+[RESOURCE_NAME]` — Displays all parent nodes of the resource
- - `resource_type:model [RESOURCE_NAME]` — Displays all models matching the name search
+- Use [selectors](/reference/node-selection/methods) (in the search bar) to select specific resources or a subset of the DAG. This can help narrow the focus on the resources that interest you. All selectors are available for use, except those requiring a state comparison (result, source status, and state). You can also use the `--exclude` and the `--select` flag (which is optional). Examples:
+ - `resource_type:model [RESOURCE_NAME]` — Returns all models matching the name search
+ - `resource_type:metric,tag:nightly` — Returns metrics with the tag `nightly`
+- Use [graph operators](/reference/node-selection/graph-operators) (in the search bar) to select specific resources or a subset of the DAG. This can help narrow the focus on the resources that interest you. Examples:
+ - `+orders` — Returns all the upstream nodes of `orders`
+ - `+dim_customers,resource_type:source` — Returns all sources that are upstream of `dim_customers`
+- Use [set operators](/reference/node-selection/set-operators) (in the search bar) to select specific resources or a subset of the DAG. This can help narrow the focus on the resources that interest you. For example:
+ - `+snowplow_sessions +fct_orders` — Use space-delineated arguments for a union operation. Returns resources that are upstream nodes of either `snowplow_sessions` or `fct_orders`.
- [View resource details](#view-resource-details) by selecting a node (double-clicking) in the graph.
- Click the List view icon in the graph's upper right corner to return to the main **Explore** page.
-
+
+### Example of lineage graph
-## Search for resources {#search-resources}
-With the search bar (on the upper left corner of the page or in a lineage graph), you can search with keywords or selectors. The resources that match your search criteria will display in a list (keyword search) or the lineage graph (selector search).
+Example of exploring the `order_items` model in the project's lineage graph:
-### Search with keywords
-When searching with keywords, dbt Explorer searches through your resource metadata, such as resource name, and returns any matches. When searching for an exact column name, the results show all relational nodes containing that column in their schemas. If there's a match, a notice in the search result indicates the resource contains the specified column.
+
-You can then refine the search results using the filters in the panel on the right-hand side of the page. Use this panel to select specific resource types or tags to apply. You can filter on model properties (access or materialization type) under the **Models** option.
+## Lenses
-### Search with selectors
+The **Lenses** feature is available from your [project's lineage graph](#project-lineage) (lower right corner). Lenses are like map layers for your DAG. Lenses make it easier to understand your project’s contextual metadata at scale, especially to distinguish a particular model or a subset of models.
-You can search with [selectors](/reference/node-selection/methods) within the full lineage graph using the search bar. Below are the selectors currently available in dbt Explorer:
+When you apply a lens, tags become visible on the nodes in the lineage graph, indicating the layer value along with coloration based on that value. If you're significantly zoomed out, only the tags and their colors are visible in the graph.
-- `fqn:` — Find resources by [file or fully qualified name](/reference/node-selection/methods#the-fqn-method). This selector is the search bar's default. If you want to use the default, it's unnecessary to add `fqn:` before the search term.
-- `source:` — Find resources by a specified [source](/reference/node-selection/methods#the-source-method).
-- `resource_type:` — Find resources by their [type](/reference/node-selection/methods#the-resource_type-method).
-- `package:` — Find resources by the [dbt package](/reference/node-selection/methods#the-package-method) that defines them.
-- `tag:` — Find resources by a specified [tag](/reference/node-selection/methods#the-tag-method).
+
-
+- **Default** (resource type)
+- **Materialization Type** (for example, identifying incremental model dependencies)
+- **Lastest Status** (for example, diagnosing a failed DAG region)
+- **Model Layer** (for example, discovering marts models to analyze)
+ - **Marts** — A model with the prefix `fct_` or `dim_` or a model that lives in the `/marts/` subdirectory.
+ - **Intermediate** — A model with the prefix `int_`. Or, a model that lives in the `/int/` or `/intermediate/` subdirectory.
+ - **Staging** — A model with the prefix `stg_`. Or, a model that lives in the `/staging/` subdirectory.
-- `group:` — Find models defined within a specified [group](/reference/node-selection/methods#the-group-method).
-- `access:` — Find models based on their [access](/reference/node-selection/methods#the-access-method) property.
+
-
+### Example of lenses
-When searching with selector methods, you can also use [graph operators](/reference/node-selection/graph-operators). For example, `+orders` returns all the upstream nodes of `orders` and `orders+1` returns just the nodes immediately downstream (the children) of `orders`.
+Example of applying the **Materialization Type** _lens_ with the lineage graph significantly zoomed out:
-You can use multiple selector methods in your search query with [set operators](/reference/node-selection/set-operators). A space implies a union set operator and a comma for an intersection. For example:
-- `resource_type:metric,tag:nightly` — Returns metrics with the tag `nightly`
-- `+snowplow_sessions +fct_orders` — Returns resources that are parent nodes of either `snowplow_sessions` or `fct_orders`
+
-
-## Browse with the sidebar
+## Keyword search {#search-resources}
+
+You can locate resources in your project by performing a keyword search in the search bar. All resource names, column names, resource descriptions, warehouse relations, and code matching your search criteria will be displayed as a list on the main (center) section of the page. When searching for an exact column name, the results show all relational nodes containing that column in their schemas. If there's a match, a notice in the search result indicates the resource contains the specified column. Also, you can apply filters to further refine your search results.
+
+
+
+- **Partial keyword search** — This is also referred to as fuzzy search.
+- **Exclude keywords** — Prepend a minus sign (-) to the keyword you want to exclude from search results. For example, `-user` will exclude all matches of that keyword from search results.
+- **Boolean operators** — Use Boolean operators to enhance your keyword search. For example, the search results for `users OR github` will include matches for either keyword.
+- **Phrase search** — Surround a string of keywords with double quotation marks to search for that exact phrase (for example, `"stg users"`). To learn more, refer to [Phrase search](https://en.wikipedia.org/wiki/Phrase_search) on Wikipedia.
+- **SQL keyword search** — Use SQL keywords in your search. For example, the search results `int github users joined` will include matches that contain that specific string of keywords (similar to phrase searching).
-By default, the catalog sidebar lists all your project’s resources. Select any resource type in the list and all those resources in the project will display as a table in the main section of the page. For a description on the different resource types (like models, metrics, and so on), refer to [About dbt projects](/docs/build/projects).
+
-To browse using a different view, you can choose one of these options from the **View by** dropdown:
+
-- **Resources** (default) — All resources in the project organized by type.
-- **Packages** — All resources in the project organized by the dbt package in which they are defined.
-- **File Tree** — All resources in the project organized by the file in which they are defined. This mirrors the file tree in your dbt project repository.
-- **Database** — All resources in the project organized by the database and schema in which they are built. This mirrors your data platform's structure that represents the [applied state](/docs/dbt-cloud-apis/project-state) of your project.
+The **Filters** side panel becomes available after you perform a keyword search. Use this panel to further refine the results from your keyword search. By default, Explorer searches across all resources in the project. You can filter on:
-
+- [Resource type](/docs/build/projects) (like models, sources, and so on)
+- [Model access](/docs/collaborate/govern/model-access) (like public, private)
+- [Model layer](/best-practices/how-we-structure/1-guide-overview) (like marts, staging)
+- [Model materialization](/docs/build/materializations) (like view, table)
+- [Tags](/reference/resource-configs/tags) (supports multi-select)
+
+Under the the **Models** option, you can filter on model properties (access or materialization type). Also available are **Advanced** options, where you can limit the search results to column name, model code, and more.
+
+
+
+### Example of keyword search
+Example of results from searching on the keyword `item` and applying the filters models, description, and code:
+
+
+
+
+## Browse with the sidebar
+
+From the sidebar, you can browse your project's resources, its file tree, and the database.
+
+- **Resources** tab — All resources in the project organized by type. Select any resource type in the list and all those resources in the project will display as a table in the main section of the page. For a description on the different resource types (like models, metrics, and so on), refer to [About dbt projects](/docs/build/projects).
+- **File Tree** tab — All resources in the project organized by the file in which they are defined. This mirrors the file tree in your dbt project repository.
+- **Database** tab — All resources in the project organized by the database and schema in which they are built. This mirrors your data platform's structure that represents the [applied state](/docs/dbt-cloud-apis/project-state) of your project.
+
+
## View model versions
@@ -130,16 +158,11 @@ You can view the definition and latest run results of any resource in your proje
The details (metadata) available to you depends on the resource’s type, its definition, and the [commands](/docs/deploy/job-commands) that run within jobs in the production environment.
+
-
-
-### Example of model details
-
-An example of the details you might get for a model:
-
-- Status bar (below the page title) — Information on the last time the model ran, whether the run was successful, how the data is materialized, number of rows, and the size of the model.
+- **Status bar** (below the page title) — Information on the last time the model ran, whether the run was successful, how the data is materialized, number of rows, and the size of the model.
- **General** tab includes:
- - **Lineage** graph — The model’s lineage graph that you can interact with. The graph includes one parent node and one child node from the model. Click the Expand icon in the graph's upper right corner to view the model in full lineage graph mode.
+ - **Lineage** graph — The model’s lineage graph that you can interact with. The graph includes one upstream node and one downstream node from the model. Click the Expand icon in the graph's upper right corner to view the model in full lineage graph mode.
- **Description** section — A [description of the model](/docs/collaborate/documentation#adding-descriptions-to-your-project).
- **Recent** section — Information on the last time the model ran, how long it ran for, whether the run was successful, the job ID, and the run ID.
- **Tests** section — [Tests](/docs/build/data-tests) for the model, including a status indicator for the latest test status. A :white_check_mark: denotes a passing test.
@@ -148,12 +171,11 @@ An example of the details you might get for a model:
- **Code** tab — The source code and compiled code for the model.
- **Columns** tab — The available columns in the model. This tab also shows tests results (if any) that you can select to view the test's details page. A :white_check_mark: denotes a passing test. To filter the columns in the resource, you can use the search bar that's located at the top of the columns view.
+
-### Example of exposure details
+
-An example of the details you might get for an exposure:
-
-- Status bar (below the page title) — Information on the last time the exposure was updated.
+- **Status bar** (below the page title) — Information on the last time the exposure was updated.
- **General** tab includes:
- **Status** section — The status on data freshness and data quality.
- **Lineage** graph — The exposure’s lineage graph. Click the Expand icon in the graph's upper right corner to view the exposure in full lineage graph mode.
@@ -161,34 +183,41 @@ An example of the details you might get for an exposure:
- **Details** section — Details like exposure type, maturity, owner information, and more.
- **Relationships** section — The nodes the exposure **Depends On**.
-### Example of test details
+
-An example of the details you might get for a test:
+
-- Status bar (below the page title) — Information on the last time the test ran, whether the test passed, test name, test target, and column name.
+- **Status bar** (below the page title) — Information on the last time the test ran, whether the test passed, test name, test target, and column name.
- **General** tab includes:
- - **Lineage** graph — The test’s lineage graph that you can interact with. The graph includes one parent node and one child node from the test resource. Click the Expand icon in the graph's upper right corner to view the test in full lineage graph mode.
+ - **Lineage** graph — The test’s lineage graph that you can interact with. The graph includes one upstream node and one downstream node from the test resource. Click the Expand icon in the graph's upper right corner to view the test in full lineage graph mode.
- **Description** section — A description of the test.
- **Recent** section — Information on the last time the test ran, how long it ran for, whether the test passed, the job ID, and the run ID.
- **Details** section — Details like schema, severity, package, and more.
- **Relationships** section — The nodes the test **Depends On**.
- **Code** tab — The source code and compiled code for the test.
+
-### Example of source details
-
-An example of the details you might get for each source table within a source collection:
+
-- Status bar (below the page title) — Information on the last time the source was updated and the number of tables the source uses.
+- **Status bar** (below the page title) — Information on the last time the source was updated and the number of tables the source uses.
- **General** tab includes:
- - **Lineage** graph — The source’s lineage graph that you can interact with. The graph includes one parent node and one child node from the source. Click the Expand icon in the graph's upper right corner to view the source in full lineage graph mode.
+ - **Lineage** graph — The source’s lineage graph that you can interact with. The graph includes one upstream node and one downstream node from the source. Click the Expand icon in the graph's upper right corner to view the source in full lineage graph mode.
- **Description** section — A description of the source.
- **Source freshness** section — Information on whether refreshing the data was successful, the last time the source was loaded, the timestamp of when a run generated data, and the run ID.
- **Details** section — Details like database, schema, and more.
- **Relationships** section — A table that lists all the sources used with their freshness status, the timestamp of when freshness was last checked, and the timestamp of when the source was last loaded.
- **Columns** tab — The available columns in the source. This tab also shows tests results (if any) that you can select to view the test's details page. A :white_check_mark: denotes a passing test.
+
+
+### Example of model details
+
+Example of the details view for the model `supplies`:
+
+
+
## Related content
- [Enterprise permissions](/docs/cloud/manage-access/enterprise-permissions)
- [About model governance](/docs/collaborate/govern/about-model-governance)
-- [What is data mesh?](https://www.getdbt.com/blog/what-is-data-mesh-the-definition-and-importance-of-data-mesh) blog
+- Blog on [What is data mesh?](https://www.getdbt.com/blog/what-is-data-mesh-the-definition-and-importance-of-data-mesh)
diff --git a/website/docs/docs/dbt-versions/release-notes/70-Apr-2024/mar-sl-updates.md b/website/docs/docs/dbt-versions/release-notes/70-Apr-2024/mar-sl-updates.md
new file mode 100644
index 00000000000..5ef4da4110e
--- /dev/null
+++ b/website/docs/docs/dbt-versions/release-notes/70-Apr-2024/mar-sl-updates.md
@@ -0,0 +1,26 @@
+---
+title: "dbt Semantic Layer updates and fixes for March 2024"
+description: "March 2024 updates for dbt Semantic Layer & MetricFlow: New export features, enhanced date filters, Tableau, Google Sheets & GraphQL API enhancements, and bug fixes."
+sidebar_label: "Updates and fixes: dbt Semantic Layer"
+sidebar_position: 10
+tags: [Mar-2024]
+date: 2024-04-01
+---
+
+The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl) and [MetricFlow](/docs/build/about-metricflow). This release note includes our work in March 2024:
+
+## New features
+
+- **Privatelink:** The Semantic Layer services now support using Privatelink for customers who have it enabled.
+- **SSO support for Semantic Layer development:** You can now develop against and test your Semantic Layer in the Cloud CLI if your developer credential uses SSO.
+
+## Updates
+
+**Entities are selectable in the Google Sheets app:** You can select entities to Group By, Filter By, and Order By.
+
+
+## Bug fixes
+
+- `dbt parse` no longer shows an error when you use a list of filters (instead of just a string filter) on a metric.
+- `join_to_timespine` now properly gets applied to conversion metric input measures.
+- Fixed an issue where exports in Redshift were not always committing to the DWH, which also had the side-effect of leaving table locks open.
diff --git a/website/docs/docs/deploy/deploy-jobs.md b/website/docs/docs/deploy/deploy-jobs.md
index ee703895f7a..cd9343efb29 100644
--- a/website/docs/docs/deploy/deploy-jobs.md
+++ b/website/docs/docs/deploy/deploy-jobs.md
@@ -113,7 +113,6 @@ You can set up a configuration where an upstream job triggers multiple downstrea
For jobs that are triggered to run by another job, a link to the upstream job run is available from your [job's run details](/docs/deploy/run-visibility#job-run-details).
-
## Related docs
- [Artifacts](/docs/deploy/artifacts)
diff --git a/website/docs/docs/deploy/job-scheduler.md b/website/docs/docs/deploy/job-scheduler.md
index 63f8a54652d..7d71aca6e23 100644
--- a/website/docs/docs/deploy/job-scheduler.md
+++ b/website/docs/docs/deploy/job-scheduler.md
@@ -29,6 +29,7 @@ Familiarize yourself with these useful terms to help you understand how the job
| Job | A collection of run steps, settings, and a trigger to invoke dbt commands against a project in the user's cloud data platform. |
| Job queue | The job queue acts as a waiting area for job runs when they are scheduled or triggered to run; runs remain in queue until execution begins. More specifically, the Scheduler checks the queue for runs that are due to execute, ensures the run is eligible to start, and then prepares an environment with appropriate settings, credentials, and commands to begin execution. Once execution begins, the run leaves the queue. |
| Over-scheduled job | A situation when a cron-scheduled job's run duration becomes longer than the frequency of the job’s schedule, resulting in a job queue that will grow faster than the scheduler can process the job’s runs. |
+| Deactivated job | A situation where a job has reached 100 consecutive failing runs. |
| Prep time | The time dbt Cloud takes to create a short-lived environment to execute the job commands in the user's cloud data platform. Prep time varies most significantly at the top of the hour when the dbt Cloud Scheduler experiences a lot of run traffic. |
| Run | A single, unique execution of a dbt job. |
| Run slot | Run slots control the number of jobs that can run concurrently. Developer plans have a fixed number of run slots, while Enterprise and Team plans have [unlimited run slots](/docs/dbt-versions/release-notes/July-2023/faster-run#unlimited-job-concurrency-for-enterprise-accounts). Each running job occupies a run slot for the duration of the run.
Team and Developer plans are limited to one project each. For additional projects, consider upgrading to the [Enterprise plan](https://www.getdbt.com/pricing/).|
@@ -82,6 +83,19 @@ The scheduler prevents queue clog by canceling runs that aren't needed, ensuring
To prevent over-scheduling, users will need to take action by either refactoring the job so it runs faster or modifying its [schedule](/docs/deploy/deploy-jobs#schedule-days).
+## Deactivation of jobs
+
+To reduce unnecessary resource consumption and reduce contention for run slots in your account, dbt Cloud will deactivate a [deploy job](/docs/deploy/deploy-jobs) or a [CI job](/docs/deploy/ci-jobs) if it reaches 100 consecutive failing runs and indicate this through the use of banners. When this happens, scheduled and triggered-to-run jobs will no longer be enqueued.
+
+To reactivate a deactivated job, you can either:
+- Update the job's settings to fix the issue and save the job (recommended)
+- Perform a manual run by clicking **Run now** on the job's page
+
+
+Example of deactivation banner on job's page:
+
+
+
## Related docs
- [dbt Cloud architecture](/docs/cloud/about-cloud/architecture#dbt-cloud-features-architecture)
- [Job commands](/docs/deploy/job-commands)
diff --git a/website/static/img/docs/collaborate/dbt-explorer/catalog-sidebar-v1.gif b/website/static/img/docs/collaborate/dbt-explorer/catalog-sidebar-v1.gif
deleted file mode 100644
index a70729382f6..00000000000
Binary files a/website/static/img/docs/collaborate/dbt-explorer/catalog-sidebar-v1.gif and /dev/null differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/example-keyword-search.png b/website/static/img/docs/collaborate/dbt-explorer/example-keyword-search.png
new file mode 100644
index 00000000000..1e98008f46d
Binary files /dev/null and b/website/static/img/docs/collaborate/dbt-explorer/example-keyword-search.png differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/example-materialization-type-lense.png b/website/static/img/docs/collaborate/dbt-explorer/example-materialization-type-lense.png
new file mode 100644
index 00000000000..6668b74ad1b
Binary files /dev/null and b/website/static/img/docs/collaborate/dbt-explorer/example-materialization-type-lense.png differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/example-model-details.png b/website/static/img/docs/collaborate/dbt-explorer/example-model-details.png
new file mode 100644
index 00000000000..c3338261b55
Binary files /dev/null and b/website/static/img/docs/collaborate/dbt-explorer/example-model-details.png differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/example-project-lineage-graph.png b/website/static/img/docs/collaborate/dbt-explorer/example-project-lineage-graph.png
new file mode 100644
index 00000000000..979781d9cc5
Binary files /dev/null and b/website/static/img/docs/collaborate/dbt-explorer/example-project-lineage-graph.png differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/example-search-sidebar.png b/website/static/img/docs/collaborate/dbt-explorer/example-search-sidebar.png
new file mode 100644
index 00000000000..45b1fd70a93
Binary files /dev/null and b/website/static/img/docs/collaborate/dbt-explorer/example-search-sidebar.png differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/lineage-v1.gif b/website/static/img/docs/collaborate/dbt-explorer/lineage-v1.gif
deleted file mode 100644
index 2772eaa9619..00000000000
Binary files a/website/static/img/docs/collaborate/dbt-explorer/lineage-v1.gif and /dev/null differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/model-resource-details-v1.gif b/website/static/img/docs/collaborate/dbt-explorer/model-resource-details-v1.gif
deleted file mode 100644
index bee4cff4bd2..00000000000
Binary files a/website/static/img/docs/collaborate/dbt-explorer/model-resource-details-v1.gif and /dev/null differ
diff --git a/website/static/img/docs/collaborate/dbt-explorer/search-v1.gif b/website/static/img/docs/collaborate/dbt-explorer/search-v1.gif
deleted file mode 100644
index 55a0d174ae4..00000000000
Binary files a/website/static/img/docs/collaborate/dbt-explorer/search-v1.gif and /dev/null differ
diff --git a/website/static/img/docs/dbt-cloud/deployment/example-deactivated-deploy-job.png b/website/static/img/docs/dbt-cloud/deployment/example-deactivated-deploy-job.png
new file mode 100644
index 00000000000..fa03302c27a
Binary files /dev/null and b/website/static/img/docs/dbt-cloud/deployment/example-deactivated-deploy-job.png differ