Merge current branch into next

.github/CODEOWNERS

@@ -1,10 +1,27 @@
 # Lower entries on this list take precedence
 
 # Anything unmatched by selectors below
-*                                     @annafil @runleonarun
+*                                     @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
+
+
+
+# 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
+
 
-# Cloud docs and images are assigned to Drew
-/website/docs/docs/dbt-cloud/dbt-cloud-changelog.md    @drewbanin @alexbethea22
-/website/docs/docs/dbt-cloud/                          @drewbanin
-/website/src/pages/dbt-cloud/                          @drewbanin
-/website/static/img/docs/dbt-cloud/                    @drewbanin

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+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

@@ -0,0 +1,54 @@
+name: Contribute to the dbt Developer Blog
+description: >
+  For proposing a new post on the dbt Developer Blog.
+labels: ["content","developer blog"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We're excited to hear about your idea for the dbt Developer Blog. This template will help lay out the proposed post and then we will work with on next steps!
+
+  - 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: checkboxes
+    id: read-contribution
+    attributes:
+      label: I have read the dbt Developer Blog contribution guidelines.
+      description: You can find the contribution guide [here](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/developer-blog.md)
+      options:
+        - label: I have read the dbt Developer Blog contribution guidelines.
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: author_type
+    attributes:
+      label: Which of these best describes you?
+      options:
+        - label: I am a dbt Community member or partner contributing to the Developer Blog
+        - label: I work for dbt Labs and am creating this issue for a community or marketing approved piece.
+    validations:
+
+
+  - type: textarea
+    attributes:
+      label: >
+        What is the topic of your post?
+      description: |
+        Please provide a short (~ 1 paragraph) summary as well as who this post is targeted towards (ie people interested in learning more about dbt snapshots or advanced Jinja users)
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Link to an initial outline.
+      description: Please link to a short outline in Notion, or Google Docs
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/improve-docs.yml

@@ -0,0 +1,42 @@
+name: Improve content
+description: Make a suggestion to improve the content in an existing page.
+labels: ["content","improvement"]
+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)
+        * 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).
+
+  - type: checkboxes
+    id: contributions
+    attributes:
+      label: Contributions
+      description: Please read the contribution docs before opening an issue or pull request.
+      options:
+        - label: I have read the contribution docs, and understand what's expected of me. 
+
+  - type: textarea
+    attributes:
+      label: Link to the page on docs.getdbt.com requiring updates
+      description: Please link to the page or pages you'd like to see improved.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What part(s) of the page would you like to see updated?
+      description: |
+        - Give as much detail as you can to help us understand the change you want to see. 
+        - Why should the docs be changed? What use cases does it support? 
+        - What is the expected outcome?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false

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

@@ -0,0 +1,42 @@
+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"]
+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)
+        * 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).
+
+  - type: checkboxes
+    id: contributions
+    attributes:
+      label: Contributions
+      description: Please read the contribution docs before opening an issue or pull request.
+      options:
+        - label: I have read the contribution docs, and understand what's expected of me. 
+
+  - type: textarea
+    attributes:
+      label: What page(s) or areas on docs.getdbt.com are affected?
+      description: Include links to pages where you're seeing a problem or making a suggestion. Also include screenshots, what browser you're using, etc.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What changes are you suggesting?
+      description: |
+        - Give as much detail as you can to help us understand the change you want to see. 
+        - Why should the docs be changed? 
+        - What is the expected outcome?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Any additional information, configuration, or data that might be necessary to reproduce the issue.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/new-dbt-feature.yml

@@ -0,0 +1,33 @@
+name: Start docs project for a new feature
+description: For dbt PMs to add docs for their new or updated dbt product features.
+labels: ["content","upcoming release"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        * 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).
+
+  - type: checkboxes
+    id: contributions
+    attributes:
+      label: Contributions
+      description: This applies to new, unreleased content.
+      options:
+        - label: I am a PM or subject matter expert at dbt who is responsible for this feature. 
+
+  - type: textarea
+    attributes:
+      label: Where does this content belong?
+      description: |
+        - Give as much detail as you can to help us understand where you expect the content to live.  
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Link to source material
+      description: |
+        Use the [source material template](https://docs.google.com/document/d/1lLWGMXJFjkY4p7r8ZKhBX73dOLmIjgXZBYq39LqmAJs/edit) to provide source material for this feature. 
+    validations:
+      required: true

.github/labeler.yml

@@ -0,0 +1,8 @@
+developer blog:
+- website/blog/**/*
+
+guides:
+- website/docs/docs/guides/**/*
+
+content:
+- website/docs/**/*

.github/pull_request_template.md

@@ -2,6 +2,8 @@
 <!---
 Describe your changes, and why you're making them. Is this linked to an open
 issue, a pull request on dbt core, etc?
+
+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
@@ -12,14 +14,10 @@ Include any notes about things that need to happen before this PR is merged, e.g
 - [ ] Ensure PR #56 is merged
 -->
 
-## Pre-release docs
-Is this change related to an unreleased version of dbt?
-- [ ] Yes: please
-    - update the base branch to `next`
-    - add Changelog components: `<Changelog>[New/Changed] in v0.x.0</Changelog>`
-    - add links to the "New and changed documentation" section of the latest [Migration Guide](../website/docs/docs/guides/migration-guide)
-- [ ] No: please ensure the base branch is `current`
-- [ ] Unsure: we'll let you know!
+## 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):
@@ -29,3 +27,4 @@ If you added new pages (delete if not applicable):
 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

.github/workflows/mark_pr_as_done.yml → .github/workflows/add_pr_to_project.yml

@@ -1,7 +1,7 @@
-name: Mark PR as done
+name: Add PR to project
 on:
-  pull_request:
-    types: [closed]
+  pull_request_target:
+    types: [opened,reopened]
 
 jobs:
   track_pr:
@@ -57,7 +57,7 @@ jobs:
         with:
           name: "data.json"
           json: ${{ steps.get_project_info.outputs.data }}
-    
+
       - name: Extract date field ID
         uses: sergeysova/jq-action@v2
         id: date_field_id
@@ -77,8 +77,8 @@ jobs:
         id: status_field_value
         with:
           cmd: 
-            jq '.organization.projectNext.fields.nodes[] | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Done") |.id' data.json
-      
+            jq '.organization.projectNext.fields.nodes[] | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Triage") |.id' data.json
+
       - name: Set fields
         id: set_fields
         uses: octokit/graphql-action@v2.x  
@@ -88,7 +88,7 @@ jobs:
               $project: ID!
               $item: ID!
               $status_field: ID!
-              $status_value: ID!
+              $status_value: String!
               $date_field: ID!
               $date_value: String!
             ) {

.github/workflows/create_next_pr.yml

@@ -0,0 +1,18 @@
+on:
+  push:
+    branches:
+    - "current"
+
+jobs:
+  pull-request:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: pull-request
+      uses: repo-sync/pull-request@v2
+      with:
+        source_branch: "current"
+        destination_branch: "next"
+        pr_title: "Merge current branch into next"
+        pr_body: "*An automated PR to keep the next branch up to date with current*"
+        github_token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/cypress_tests.yml

@@ -0,0 +1,47 @@
+name: cypress tests
+
+on:
+  pull_request:
+    branches:
+      - current
+
+jobs:
+  start-workflow:
+    name: start workflow
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+
+      - name: install node
+        uses: actions/setup-node@v2
+        with:
+          node-version: '16.13.1'
+
+      - name: npm install
+        run: cd website && npm ci
+
+      - name: setup env
+        run: |
+          PR_NUMBER=$(jq --raw-output .pull_request.number ${{ github.event_path }})
+          echo "PR_NUMBER=${PR_NUMBER}" >> ${GITHUB_ENV}
+
+      - name: run cypress e2e 
+        uses: cypress-io/github-action@v4
+        with:
+          command: npx cypress run
+          browser: chrome
+          working-directory: website
+          spec: cypress/e2e/*.cy.js
+          wait-on: https://deploy-preview-${{ env.PR_NUMBER }}--docs-getdbt-com.netlify.app
+          wait-on-timeout: 600
+        env:
+          CYPRESS_BASE_URL: https://deploy-preview-${{ env.PR_NUMBER }}--docs-getdbt-com.netlify.app
+
+      - name: Screenshot artifact upload
+        uses: actions/upload-artifact@v2
+        if: failure()
+        with:
+          name: cypress-screenshots
+          path: cypress/screenshots