Merge branch 'current' into new-state

README.md

@@ -56,9 +56,9 @@ You can click a link available in a netlify bot PR comment to see and review you
 2. Clone this repo: `git clone https://github.com/dbt-labs/docs.getdbt.com.git`
 3. `cd` into the repo: `cd docs.getdbt.com`
 4. `cd` into the `website` subdirectory: `cd website`
-5. Install the required node packages: `npm install` (optional — install any updates)
-6. Build the website: `npm start`
-7. Before pushing your changes to a branch, check that all links work by using the `make build` script.
+5. Install the required node packages: `make install` or `npm install` (optional — install any updates)
+6. Build the website: `make run` or `npm start`
+7. Before pushing your changes to a branch, run `make build` or `npm run build` and check that all links work
 
 Advisory:
 - If you run into an `fatal error: 'vips/vips8' file not found` error when you run `npm install`, you may need to run `brew install vips`. Warning: this one will take a while -- go ahead and grab some coffee!

website/Makefile

@@ -0,0 +1,10 @@
+.PHONY: run install build
+
+run:
+	npm start
+
+install:
+	npm install
+
+build:
+	DOCS_ENV=build npm run build

website/blog/2022-05-03-making-dbt-cloud-api-calls-using-dbt-cloud-cli.md

@@ -109,7 +109,7 @@ After the initial release I started to expand to cover the rest of the dbt Cloud
 
 In this example we’ll download a `catalog.json` artifact from the latest run of a dbt Cloud job using `dbt-cloud run list` and `dbt-cloud get-artifact` and then write a simple Data Catalog CLI application using the same tools that are used in `dbt-cloud-cli` (i.e., `click` and `pydantic`). Let’s dive right in!
 
-The first command we need is the `dbt-cloud run list` which uses an [API endpoint](https://docs.getdbt.com/dbt-cloud/api-v2#/operations/List%20Runs) that returns runs sorted by creation date, with the most recent run appearing first. The command returns a JSON response that has one top-level attribute `data` that contains a list of runs. We’ll need to extract the `id` attribute of the first one and to do that we use [jq](https://stedolan.github.io/jq/):
+The first command we need is the `dbt-cloud run list` which uses an [API endpoint](https://docs.getdbt.com/dbt-cloud/api-v2-legacy#/operations/List%20Runs) that returns runs sorted by creation date, with the most recent run appearing first. The command returns a JSON response that has one top-level attribute `data` that contains a list of runs. We’ll need to extract the `id` attribute of the first one and to do that we use [jq](https://stedolan.github.io/jq/):
 
 ```
 latest_run_id=$(dbt-cloud run list --job-id $DBT_CLOUD_JOB_ID | jq .data[0].id -r)

website/blog/authors.yml

@@ -373,6 +373,15 @@ pat_kearns:
   name: Pat Kearns
   organization: dbt Labs
 
+rastislav_zdechovan:
+  image_url: /img/blog/authors/rastislav-zdechovan.png
+  job_title: Analytics Engineer
+  links:
+    - icon: fa-linkedin
+      url: https://www.linkedin.com/in/rastislav-zdechovan/
+  name: Rastislav Zdechovan
+  organization: Infinite Lambda
+
 ross_turk:
   image_url: /img/blog/authors/ross-turk.png
   job_title: VP Marketing

website/dbt-versions.js

@@ -31,6 +31,14 @@ exports.versions = [
 ]
 
 exports.versionedPages = [
+  {
+    "page": "reference/resource-properties/deprecation_date", 
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "reference/commands/retry",
+    "firstVersion": "1.6",
+  },
   {
     "page": "docs/build/groups",
     "firstVersion": "1.5",
@@ -115,11 +123,67 @@ exports.versionedPages = [
     "page": "reference/dbt-jinja-functions/print",
     "firstVersion": "1.1",
   },
+  {
+    "page": "docs/build/build-metrics-intro",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/sl-getting-started",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/about-metricflow",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/join-logic",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/validation",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/semantic-models",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/group-by",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/entities",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/metrics-overview",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/cumulative",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/derived",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/measure-proxy",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/ratio",
+    "firstVersion": "1.6",
+  },
 ]
 
 exports.versionedCategories = [
   {
     "category": "Model governance",
     "firstVersion": "1.5",
+  },
+  {
+    "category": "Build your metrics",
+    "firstVersion": "1.6",
   }
 ]

website/docs/community/resources/code-of-conduct.md

@@ -1,50 +1,42 @@
 ---
 title: "Code of Conduct"
 id: "code-of-conduct"
+description: "Learn about the community values that shape our rules, and review our anti-harassment policy."
 ---
 
 # dbt Community Code of Conduct
 
-dbt has a supportive, active community of thousands of smart, kind, and helpful people who share a commitment to elevating the analytics profession.
+This Code of Conduct applies to all dbt Community spaces, both online and offline. This includes Slack, Discourse, code repositories (dbt Core, dbt packages, etc.), Office Hours, and Meetups. Participants are responsible for knowing and abiding by this Code of Conduct.
 
-You can get involved in the dbt community by connecting at [events](/community/events), getting or giving help in any of our many channels, contributing to dbt or a dbt package, and many other ways.
-
-People genuinely love this community, and we are committed to maintaining the spirit of it. As such have written this Code of Conduct to help all participants understand how to best participate in our community.
-
-The Code of Conduct applies to all dbt Community spaces both online and off. This includes: Slack, Discourse, code repositories (dbt Core, dbt packages etc), Office Hours and Meetups. There are some guidelines specific to particular forums (listed below). Participants are responsible for knowing and abiding by this Code of Conduct.
-
-This Code of Conduct has three sections:
+This Code of Conduct has two sections:
 
 - **dbt Community Values:** These values apply to all of our community spaces, and all of our guidelines are based on these values.
-- **Forum-specific guidelines**: These guidelines explain some of the cultural norms that apply to specific forums.
 - **Anti-harassment policy:**  We are dedicated to providing a harassment-free experience for everyone in our community — here, we outline exactly what that means.
 
 We appreciate your support in continuing to build a community we’re all proud of.
 
 — The dbt Community Admin Team.
 
 ## dbt Community Values
+### Create more value than you capture.
 
-### Be respectful.
-
-We want everyone to have a fulfilling and positive experience in the dbt Community and we are continuously grateful in your help ensuring that this is the case.
-
-Be courteous, respectful, and polite to fellow community members. Generally, don’t be a jerk.
-
-Be considerate of others’ time — many people in the community generously give their time for free.
+Each community member should strive to create more value in the community than they capture. This is foundational to being a community.
 
 Ways to demonstrate this value:
 
-- Take the time to write bug reports well ([example](https://github.com/fishtown-analytics/dbt/issues/2370))
-- Thank people if they help solve a problem.
+- [Coding contributions](/community/contributing/contributing-coding): Contribute to dbt Core, a package, or an adapter. Beyond implementing new functionality, you can also open issues or participate in discussions.
+- [Writing contributions](/community/contributing/contributing-writing): You can suggest edits to every page of the dbt documentation, or suggest a topic for the dbt Developer Blog. 
+- [Join in online](/community/contributing/contributing-online-community): Ask and answer questions on the Discourse forum, kick off a lively discussion in Slack, or even maintain a Slack channel of your own. 
+- [Participate in events](/community/contributing/contributing-realtime-events): Organise a community Meetup, speak at an event, or provide office space/sponsorship for an existing event. 
 
 ### Be you.
 
 Some developer communities allow and even encourage anonymity — we prefer it when people identify themselves clearly. It helps to build empathy, and form relationships.
 
 Ways to demonstrate this value:
 
-- Update your profile on any dbt Community forums to include your name, and a clear picture. On Slack, use the “what I do” section to add your role title and current company
+- Update your profile on dbt Community platforms to include your name and a clear picture of yourself. Where available, use the "what I do" section to add your role, title and current company.
+- Join your `#local-` channel in Slack, or if it doesn't exist then propose a new one. 
 - Write in your own voice, and offer your own advice, rather than speaking in your company’s marketing or support voice.
 
 ### Encourage diversity and participation.
@@ -57,81 +49,27 @@ Ways to demonstrate this value:
 - Demonstrate empathy for a community member’s experience — not everyone comes from the same career background, so adjust answers accordingly.
 - If you are sourcing speakers for events, put in additional effort to find speakers from underrepresented groups.
 
-### Create more value than you capture.
-
-Each community member should strive to create more value in the community than they capture. This is foundational to being a community.
-
-Ways to demonstrate this value:
-
-- Contribute to dbt or a dbt package
-- Participate in discussions on Slack and Discourse
-- Share things you have learned on Discourse
-- Host events
-
-Be mindful that others may not want their image or name on social media, and when attending or hosting an in-person event, ask permission prior to posting about another person.
-
 ### Be curious.
 
-Always ask yourself “why?” and strive to be continually learning.
+Always ask yourself "why?" and strive to be continually learning.
 
 Ways to demonstrate this value:
 
-- Try solving a problem yourself before asking for help, e.g. rather than asking “what happens when I do X”, experiment and observe the results!
-- When asking questions, explain the “why” behind your decisions, e.g. “I’m trying to solve X problem, by writing Y code. I’m getting Z problem”
-- When helping someone else, explain why you chose that solution, or if no solution exists, elaborate on the reason for that, e.g. “That’s not possible in dbt today — but here’s a workaround / check out this GitHub issue for a relevant discussion”
-
-## Guidelines
-
-### Participating in Slack
-
-dbt Slack is where the dbt community hangs out, discusses issues, and troubleshoots problems together. It is not a support service — please do not treat it like one.
-
-We also have a number of cultural norms in our Slack community. You must read and agree to the rules before joining Slack, but you can also find them [here](/community/resources/slack-rules-of-the-road/).
-
-As a short summary:
-
-- [Rule 1: Be respectful](/community/resources/slack-rules-of-the-road/#rule-1-be-respectful)
-- [Rule 2: Use the right channel](/community/resources/slack-rules-of-the-road/#rule-2-use-the-right-channel)
-- [Rule 3: Put effort into your question](/community/resources/slack-rules-of-the-road/#rule-3-put-effort-into-your-question)
-- [Rule 4: Do not double-post](/community/resources/slack-rules-of-the-road/#rule-4-do-not-double-post)
-- [Rule 5: Keep it in public channels](/community/resources/slack-rules-of-the-road/#rule-5-keep-it-in-public-channels)
-- [Rule 6: Do not solicit members of our Slack](/community/resources/slack-rules-of-the-road/#rule-6-do-not-solicit-members-of-our-slack)
-- [Rule 7: Do not demand attention with @channel and @here, or by tagging individuals](/community/resources/slack-rules-of-the-road/#rule-7-do-not-demand-attention-with-channel-and-here-or-by-tagging-individuals)
-- [Rule 8: Use threads](/community/resources/slack-rules-of-the-road/#rule-8-use-threads)
-
-### Vendor guidelines
-
-If you are a vendor (i.e. you represent an organization that sells a product or service relevant to our community), then there are additional guidelines you should be aware of.
-
-Most importantly — do not solicit members of our community as lead generation. You can find the rest of these [here](/community/resources/vendor-guidelines).
-
-### Guideline violations — 3 strikes method
-
-The point of our guidelines is not to find opportunities to punish people, but we do need a fair way to deal with people who do harm to our community. Violations related to our anti-harassment policy (below) will be addressed immediately and are not subject to 3 strikes.
-
-1. First occurrence: We’ll give you a friendly, but public, reminder that the behavior is inappropriate according to our guidelines.
-2. Second occurrence: We’ll send you a private message with a warning that any additional violations will result in removal from the community.
-3. Third occurrence: Depending on the violation, we might need to delete or ban your account.
-
-Notes:
-
-- Obvious spammers are banned on first occurrence.
-- Participation in the dbt Community is a privilege — we reserve the right to remove people from the community.
-- Violations are forgiven after 6 months of good behavior, and we won’t hold a grudge.
-- People who are committing minor formatting / style infractions will get some education, rather than hammering them in the 3 strikes process.
-- Contact conduct@getdbt.com to report abuse or appeal violations. In the case of appeals, we know that mistakes happen, and we’ll work with you to come up with a fair solution if there has been a misunderstanding.
+- Try solving a problem yourself before asking for help, e.g. rather than asking "what happens when I do X", experiment and observe the results!
+- When asking questions, explain the "why" behind your decisions, e.g. "I’m trying to solve X problem, by writing Y code. I’m getting Z problem"
+- When helping someone else, explain why you chose that solution, or if no solution exists, elaborate on the reason for that, e.g. "That’s not possible in dbt today — but here’s a workaround / check out this GitHub issue for a relevant discussion"
 
 ## Anti-harassment policy
 
-Further to our guidelines for participating in the community in a positive manner, we are also dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment of participants in any form.
+We are dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment of participants in any form.
 
 Harassment includes:
 
 - Offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, age, race, or religion.
 - Unwelcome comments regarding a person’s lifestyle choices and practices, including those related to food, health, parenting, drugs, and employment.
 - Deliberate misgendering or use of ‘dead’ or rejected names.
 - Gratuitous or off-topic sexual images or behaviour in spaces where they’re not appropriate.
-- Physical contact and simulated physical contact (eg, textual descriptions like “*hug*” or “*backrub*”) without consent or after a request to stop.
+- Physical contact and simulated physical contact (eg, textual descriptions like "*hug*" or "*backrub*") without consent or after a request to stop.
 - Threats of violence.
 - Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
 - Deliberate intimidation.
@@ -141,19 +79,21 @@ Harassment includes:
 - Unwelcome sexual attention.
 - Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
 - Continued one-on-one communication after requests to cease.
-- Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary to protect vulnerable people from intentional abuse.
+- Deliberate "outing" of any aspect of a person’s identity without their consent except as necessary to protect vulnerable people from intentional abuse.
 - Publication of non-harassing private communication.
 
+Be mindful that others may not want their image or name on social media. Ask permission prior to posting about another person at in-person events.
+
 The dbt Community prioritizes marginalized people’s safety over privileged people’s comfort. The dbt Community Admin team reserves the right not to act on complaints regarding:
 
 - ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’
-- Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you.”
+- Reasonable communication of boundaries, such as "leave me alone," "go away," or "I’m not discussing this with you."
 - Communicating in a ‘tone’ you don’t find congenial
 - Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions
 
 ### Reporting harassment
 
-If you are being harassed by a member of the dbt Community, notice that someone else is being harassed, or have any other concerns, please contact us at [community@dbtlabs.com](mailto:community@dbtlabs.com).
+If you are being harassed by a member of the dbt Community, notice that someone else is being harassed, or have any other concerns, please contact us at [community@dbtlabs.com](mailto:community@dbtlabs.com) or use the workflows in [#moderation-and-administration](https://getdbt.slack.com/archives/C02JJ8N822H) on Slack.
 
 We will respect confidentiality requests for the purpose of protecting victims of abuse. At our discretion, we may publicly name a person about whom we’ve received harassment complaints, or privately warn third parties about them, if we believe that doing so will increase the safety of dbt community members or the general public. We will not name harassment victims without their affirmative consent.