Merge branch 'current' into patch-1

.github/CODEOWNERS

@@ -1,27 +1,20 @@
 # Lower entries on this list take precedence
 
 # Anything unmatched by selectors below
-*                                     @runleonarun
-
-# Cloud docs and images are assigned to Leona
-/website/docs/docs/dbt-cloud/dbt-cloud-changelog.md    @runleonarun 
-/website/docs/docs/dbt-cloud/                          @runleonarun 
-/website/src/pages/dbt-cloud/                          @runleonarun 
-/website/static/img/docs/dbt-cloud/                    @runleonarun 
-
-# Blog content assigned to Developer experience team
-/website/blog/                       @runleonarun
+*      @dbt-labs/product-docs
 
+# The blog 
+/website/blog @KiraFuruichi
 
 
 # Adapter & Package Development Docs
-/website/docs/docs/supported-data-platforms.md/                       @runleonarun @dataders
-/website/docs/reference/warehouse-profiles/                     @runleonarun @dataders
-/website/docs/reference/resource-configs/                       @runleonarun @dataders
-/website/docs/guides/building-packages                          @runleonarun @amychen1776 @dataders @dbeatty10
-/website/docs/contributing/building-a-new-adapter               @runleonarun @dataders @dbeatty10
-/website/docs/contributing/testing-a-new-adapter                @runleonarun @dataders @dbeatty10
-/website/docs/guides/creating-new-materializations              @runleonarun @dataders @dbeatty10
-/website/docs/docs/dbt-cloud/cloud-configuring-dbt-cloud/       @runleonarun @dataders @dbeatty10
+/website/docs/docs/supported-data-platforms.md                @dbt-labs/product-docs @dataders
+/website/docs/reference/warehouse-setups                      @dbt-labs/product-docs @dataders
+# `resource-configs` contains more than just warehouse setups
+/website/docs/reference/resource-configs/*-configs.md           @dbt-labs/product-docs @dataders
+/website/docs/guides/advanced/adapter-development              @dbt-labs/product-docs @dataders @dbeatty10
+
+/website/docs/guides/building-packages                          @dbt-labs/product-docs @amychen1776 @dataders @dbeatty10
+/website/docs/guides/creating-new-materializations              @dbt-labs/product-docs @dataders @dbeatty10
 
 

.github/ISSUE_TEMPLATE/improve-docs.yml → .github/ISSUE_TEMPLATE/a-improve-docs.yml

@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        * You can ask questions or submit ideas for the dbt docs in [Discussions](https://github.com/dbt-labs/docs.getdbt.com/discussions)
+        * You can ask questions or submit ideas for the dbt docs in [Issues](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose)
         * Before you file an issue read the [Contributing guide](https://github.com/dbt-labs/docs.getdbt.com#contributing).
         * Check to make sure someone hasn't already opened a similar [issue](https://github.com/dbt-labs/docs.getdbt.com/issues).
 
@@ -39,4 +39,4 @@ body:
       label: Additional information
       description: Add any other context or screenshots about the feature request here.
     validations:
-      required: false
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,5 @@
 blank_issues_enabled: true
 contact_links:
-  - name: Want to see new content? Open a discussion!
-    url: https://github.com/dbt-labs/docs.getdbt.com/discussions/new
-    about: You can open a discussion to propose new content for the dbt product documentation.
   - name: Have questions about dbt? Join the Community!
     url: https://www.getdbt.com/community/join-the-community
     about: You can join the dbt Labs Community to ask and answer questions.

.github/ISSUE_TEMPLATE/contribute-to-developer-blog.yml

@@ -1,4 +1,4 @@
-name: Contribute to the dbt Developer Blog
+name: Propose a dbt Developer Blog idea
 description: >
   For proposing a new post on the dbt Developer Blog.
 labels: ["content","developer blog"]

.github/ISSUE_TEMPLATE/improve-the-site.yml

@@ -1,11 +1,11 @@
-name: Improve the docs.getdbt.com site
-description: Make a suggestion or report a problem about the technical implementation of docs.getdbt.com.
-labels: ["engineering"]
+name: Report a docs.getdbt.com site issue
+description: Report a problem about the technical implementation of docs.getdbt.com.
+labels: ["engineering","bug"]
 body:
   - type: markdown
     attributes:
       value: |
-        * You can ask questions or submit ideas for the dbt docs in [Discussions](https://github.com/dbt-labs/docs.getdbt.com/discussions)
+        * You can ask questions or submit ideas for the dbt docs in [Issues](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose)
         * Before you file an issue read the [Contributing guide](https://github.com/dbt-labs/docs.getdbt.com#contributing).
         * Check to make sure someone hasn't already opened a similar [issue](https://github.com/dbt-labs/docs.getdbt.com/issues).
 
@@ -39,4 +39,4 @@ body:
       label: Additional information
       description: Any additional information, configuration, or data that might be necessary to reproduce the issue.
     validations:
-      required: false
+      required: false

.github/ISSUE_TEMPLATE/zzz_add-adapter-to-trusted-list.yml

@@ -0,0 +1,62 @@
+name: Add adapter to Trusted list
+description: For adapter maintainers who wish to have theirs added to the list of Trusted adapters.
+title: "Trust dbt-myadapter"
+labels: ["adapter maintainers"]
+assignees:
+  - dataders
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We're excited that you'd like to support your adapter formally as "Trusted"! This template will ensure that you are aware of the process and the guidelines. Additionally, that you can vouch that your adapter currently meets the standards of a Trusted adapter. For more information, see [Trusted adapters](https://docs.getdbt.com/docs/trusted-adapters)
+
+  - type: input
+    id: adapter-repo
+    attributes:
+      label: Link to adapter repo
+      description: Please link to the GitHub repo
+    validations:
+      required: true
+
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you?
+      placeholder: your preferred email and/or dbt Slack handle
+    validations:
+      required: true
+
+  - type: dropdown
+    id: author_type
+    attributes:
+      label: Which of these best describes you?
+      options:
+        - I am a dbt Community member
+        - I work for the vendor on top of which the dbt adapter functions
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: read-program-guide
+    attributes:
+      label: Please agree to the each of the following
+      options:
+        - label: I am a maintainer of the adapter being submited for Trusted status
+          required: true
+        - label: I have read both the [Trusted adapters](https://docs.getdbt.com/docs/trusted-adapters) and [Building a Trusted Adapter](https://docs.getdbt.com/guides/dbt-ecosystem/adapter-development/8-building-a-trusted-adapter) pages.
+          required: true
+        - label: I believe that the adapter currently meets the expectations given above
+          required: true
+        - label: I will ensure this adapter stays in compliance with the guidelines
+          required: true
+        - label: I understand that dbt Labs reserves the right to remove an adapter from the trusted adapter list at any time, should any of the below guidelines not be met
+          required: true
+
+  - type: textarea
+    id: icon
+    attributes:
+      label: What icon should be used?
+      description: |
+        Please share an svg image that you'd like to be displayed in for your adapter. Normally, this is the logo for the data platform on top of which your adapter works. If there's a dark mode version, please also share that.
+        Pasting the image from your clipboard will upload the file to GitHub and create markdown formatting for it to be rendered inline

.github/config.yml

@@ -0,0 +1,14 @@
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+  Hello!👋 Thanks for contributing to the dbt product documentation and opening this pull request! ✨ 
+  
+  We use Markdown and some HTML to write the dbt product documentation. When writing content, you can use our [style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [content types](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-types.md) to understand our writing standards and how we organize information in the dbt product docs.
+  
+  We'll review your contribution and respond as soon as we can. 😄
+  
+  
+
+
+

.github/labeler.yml

@@ -2,7 +2,10 @@ developer blog:
 - website/blog/**/*
 
 guides:
-- website/docs/docs/guides/**/*
+- website/docs/guides/**/*
+- website/docs/quickstarts/**/*
 
 content:
 - website/docs/**/*
+- website/snippets/**/*
+- website/static/**/*

.github/lychee.toml

@@ -0,0 +1,54 @@
+###
+### Display
+###
+
+# Verbose program output
+# Accepts log level: "error", "warn", "info", "debug", "trace"
+verbose = "info"
+
+# Don't show interactive progress bar while checking links.
+no_progress = true
+
+###
+### Cache
+###
+
+# Enable link caching. This can be helpful to avoid checking the same links on
+# multiple runs.
+cache = false
+
+###
+### Requests
+###
+
+# Website timeout from connect to response finished.
+timeout = 30
+
+# Comma-separated list of accepted status codes for valid links.
+accept = [200, 403, 429]
+
+# Base URL or website root directory to check relative URLs.
+base = "https://docs.getdbt.com"
+
+###
+### Exclusions
+###
+
+# Exclude URLs from checking (supports regex)
+exclude = [
+  'frontMatter.',
+  'https://badge.fury.io',
+  'https://img.shields.io',
+  'https://gitlab.com',
+  'https://dbtlabs.postman.co',
+  'https://mobile.twitter.com',
+  'https://twitter.com',
+  'https://www.twitter.com',
+]
+
+# Exclude all mail addresses from checking
+exclude_mail = true
+
+# Check links inside `<code>` and `<pre>` blocks as well as Markdown code
+# blocks.
+include_verbatim = false

.github/pull_request_template.md

@@ -1,30 +1,25 @@
-## Description & motivation
+## What are you changing in this pull request and why?
 <!---
-Describe your changes, and why you're making them. Is this linked to an open
-issue, a pull request on dbt core, etc?
+Describe your changes and why you're making them. If linked 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).
 -->
 
-## To-do before merge
-<!---
-(Optional -- remove this section if not needed)
-Include any notes about things that need to happen before this PR is merged, e.g.:
-- [ ] Change the base branch
-- [ ] Ensure PR #56 is merged
+## Checklist
+<!--
+Uncomment if you're publishing docs for a prerelease version of dbt (delete if not applicable):
+- [ ] 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/guides/migration/versions)
 -->
+- [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines.
+- [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
 
-## Prerelease docs
-If this change is related to functionality in a prerelease version of dbt (delete if not applicable):
-- [ ] I've added versioning components, as described in ["Versioning Docs"](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/versioningdocs.md)
-- [ ] I've added a note to the prerelease version's [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
-
-## Checklist
-If you added new pages (delete if not applicable):
-- [ ] The page has been added to `website/sidebars.js`
-- [ ] The new page has a unique filename
+Adding new pages (delete if not applicable):
+- [ ] Add page to `website/sidebars.js`
+- [ ] Provide a unique filename for the new page
 
-If you removed existing pages (delete if not applicable):
-- [ ] The page has been removed from `website/sidebars.js`
-- [ ] An entry has been added to `_redirects`
-- [ ] [Run link testing](https://github.com/dbt-labs/docs.getdbt.com#running-the-cypress-tests-locally) to update the links that point to the deleted page
+Removing or renaming existing pages (delete if not applicable):
+- [ ] Remove page from `website/sidebars.js`
+- [ ] Add an entry `website/static/_redirects`
+- [ ] [Ran link testing](https://github.com/dbt-labs/docs.getdbt.com#running-the-cypress-tests-locally) to update the links that point to the deleted page

.github/teams.yml

@@ -0,0 +1,5 @@
+Docs team:
+  - '@runleonarun'
+  - '@mirnawong1'
+  - '@nghi-ly'
+  - '@matthewshaver'