This branch was auto-updated!

License.md

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright {yyyy} {name of copyright owner}
+   Copyright \{yyyy\} \{name of copyright owner\}
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

contributing/adding-page-components.md

@@ -4,20 +4,20 @@ You can use the following components to provide code snippets for each supported
 
 Identify code by labeling with the warehouse names:
 
-```js
+```code
         <WHCode>
 
         <div warehouse="warehouse#1">
 
-        ```sql
+        ```
         select * from `dbt-tutorial.jaffle_shop.customers`
         ```
 
         </div>
 
         <div warehouse="warehouse#2">
 
-        ```sql
+        ```
         select * from default.jaffle_shop_customers
         ```
 
@@ -45,11 +45,11 @@ Identify code and code files by labeling with the component they are describing:
 
         <File name='models/<modelname>.sql'>
 
-        ```sql
+        ```
 
-        {{ config(
+        \{\{ config(
 
-        ) }}
+        ) \}\}
 
         select ...
 
@@ -60,9 +60,9 @@ Identify code and code files by labeling with the component they are describing:
 
         <File name='dbt_project.yml'>
 
-        ```yml
+        ```
         models:
-        [<resource-path>](/reference/resource-configs/resource-path):
+        [resource-path](/reference/resource-configs/resource-path):
 
 
         ```
@@ -75,9 +75,9 @@ Identify code and code files by labeling with the component they are describing:
 
         <File name='dbt_project.yml'>
 
-        ```yml
+        ```
         sources:
-        [<resource-path>](/reference/resource-configs/resource-path):
+        [resource-path](/reference/resource-configs/resource-path):
 
 
         ```

contributing/content-style-guide.md

@@ -359,10 +359,10 @@ There won't be many instances where you need to display 4 or 5 cards on the docs
 
 Otherwise, the text will appear squished and provide users with a bad experience.
 
-- `<divclassName="grid--2-col">`: creates 2 column cards
-- `<divclassName="grid--3-col">`: creates 3 columns cards
-- `<divclassName="grid--4-col">`: creates 4 columns cards (use sparingly)
-- `<divclassName="grid--5-col">`: creates 5 columns cards (use sparingly)
+- `<div className="grid--2-col">`: creates 2 column cards
+- `<div className="grid--3-col">`: creates 3 columns cards
+- `<div className="grid--4-col">`: creates 4 columns cards (use sparingly)
+- `<div className="grid--5-col">`: creates 5 columns cards (use sparingly)
 - You can't create cards with 6 or more columns as that would provide users a poor experience.
 
 Refer to [dbt Cloud features](/docs/cloud/about-cloud/dbt-cloud-features) and [Quickstarts](/docs/guides) as examples. 
@@ -456,7 +456,7 @@ In general, when the spelling of English words varies by locale &mdash; use the
 standardize  | standardise 
 license | licence
 color | colour
-</div></b>
+<b>
 
 Avoid regional idiomatic phrases as well.  For example, a common saying amongst English speakers in India is "do the needful," but this phrase may be unrecognizable to English speakers from other regions. 
 
@@ -533,7 +533,7 @@ terminal | shell
 username | login
 dbt Cloud CLI | CLI, dbt CLI
 dbt Core | CLI, dbt CLI
-</div></b>
+</b>
 
 Note, let's make sure we're talking to our readers and keep them close to the content and documentation (second person). 
 

contributing/lightbox.md

@@ -14,14 +14,15 @@ You can use the Lightbox component to add an image or screenshot to your page. I
 
 ## Example usage
 
-<code><Lightbox</code><br>
-<code>src="/img/hamburger-icon.jpg"</code><br>
-<code>lt="Alt text"</code><br>
-<code>title="This text is visible"</code><br> 
-<code>collapsed={true}</code><br>
-<code>width="600px"</code><br>
-<code>alignment="left"</code><br>
-<code>/></code>
-
+```mdx
+<Lightbox
+  src="/img/hamburger-icon.jpg"
+  lt="Alt text"
+  title="This text is visible" 
+  collapsed={true}
+  width="600px"
+  alignment="left"
+/>
+```
 
 <LoomVideo id="2b64dbd47a2d46dbafa5b43ed52a91e0" />   

contributing/single-sourcing-content.md

@@ -107,7 +107,7 @@ Below is how we can implement the same versioning using the new **VersionBlock**
 
 You see this block when the selected version is >= 0.21:
 
-```markdown
+```code
 
 <VersionBlock firstVersion="0.21">
 
@@ -116,11 +116,12 @@ $ dbt run --select [...] --defer --state path/to/artifacts
 $ dbt test --select [...] --defer --state path/to/artifacts
 \```
 
-```
 </VersionBlock>
-You see this version block when the selected version is <= 0.20
+```
 
-```markdown
+You see this version block when the selected version is `<= 0.20`
+
+```code
 <VersionBlock lastVersion="0.20">
 
 ```shell

website/blog/2021-09-11-sql-dateadd.md

@@ -6,7 +6,7 @@ canonical_url: https://docs.getdbt.com/sql-reference/dateadd
 
 authors: david_krevitt
 
-tags: [SQL magic]
+tags: [sql magic]
 hide_table_of_contents: false
 
 date: 2021-11-15

website/blog/2021-09-11-union-all.md

@@ -5,7 +5,7 @@ slug: sql-union-all
 
 authors: david_krevitt
 
-tags: [SQL magic]
+tags: [sql magic]
 hide_table_of_contents: false
 
 date: 2021-11-15

website/blog/2021-11-22-exact-commands-we-run-in-production.md

@@ -42,7 +42,7 @@ Some projects can afford to have older data in the warehouse, others can’t.
 
 ### 3) Simplify your regularly scheduled runs
 
-The more complex your run commands are, the harder it gets to maintain this in the long run. Feel free to rely on dbt’s DAG (more info on why we <3 DAGs in my colleagues Christine + Randy’s [modular data modeling technique](https://getdbt.com/analytics-engineering/modular-data-modeling-technique/) post).
+The more complex your run commands are, the harder it gets to maintain this in the long run. Feel free to rely on dbt’s DAG (more info on why we &lt;3 DAGs in my colleagues Christine + Randy’s [modular data modeling technique](https://getdbt.com/analytics-engineering/modular-data-modeling-technique/) post).
 
 Given those principles, we’ll now take a look at the most common run commands for production jobs, and why we think they could work for your organization! Do note that yours may vary slightly (depending on your team’s specific needs), but as long as you stick to the principles mentioned above, your project should be in good shape!
 

website/blog/2021-11-29-the-missing-role-of-design-in-analytics.md

@@ -41,40 +41,28 @@ One solution I proposed back in 2019 is hiring a [data product manager](https://
 
 <table>
   <tr>
-   <td>Don’t
-   </td>
-   <td>Do
-   </td>
+   <td>Don’t</td>
+   <td>Do</td>
   </tr>
   <tr>
-   <td>Think only within the constraints of your current tooling.
-   </td>
-   <td>First define the ideal user experience, irrespective of tooling.  
-   </td>
+   <td>Think only within the constraints of your current tooling.</td>
+   <td>First define the ideal user experience, irrespective of tooling.</td>
   </tr>
   <tr>
-   <td>Think users can simply build their own solution given a self-service interface.
-   </td>
-   <td>Recognize that hard ongoing problems require a design-focused analyst.
-   </td>
+   <td>Think users can simply build their own solution given a self-service interface.</td>
+   <td>Recognize that hard ongoing problems require a design-focused analyst.</td>
   </tr>
   <tr>
-   <td>Stop at the data visualization.
-   </td>
-   <td>Think about how to group visualizations, the interactions, and purpose-built exploratory flows.
-   </td>
+   <td>Stop at the data visualization.</td>
+   <td>Think about how to group visualizations, the interactions, and purpose-built exploratory flows.</td>
   </tr>
   <tr>
-   <td>Ignore look and feel.
-   </td>
-   <td>Think about the overall aesthetics of your output.
-   </td>
+   <td>Ignore look and feel.</td>
+   <td>Think about the overall aesthetics of your output.</td>
   </tr>
   <tr>
-   <td>Just respond to tickets and user requests.
-   </td>
-   <td>Truly try to understand the problem and design the appropriate solution.
-   </td>
+   <td>Just respond to tickets and user requests.</td>
+   <td>Truly try to understand the problem and design the appropriate solution.</td>
   </tr>
 </table>
 
@@ -104,58 +92,40 @@ Here are a few examples:
 
 <table>
   <tr>
-   <td><strong>Traditional Dashboards</strong>
-   </td>
-   <td><strong>Analytical Applications</strong>
-   </td>
+   <td><strong>Traditional Dashboards</strong></td>
+   <td><strong>Analytical Applications</strong></td>
   </tr>
   <tr>
-   <td>Built for generic use cases
-   </td>
-   <td>Purpose-built for specific use cases
-   </td>
+   <td>Built for generic use cases</td>
+   <td>Purpose-built for specific use cases</td>
   </tr>
   <tr>
-   <td>Standard dashboard interactions
-   </td>
-   <td>Interactive based on the desired workflow
-   </td>
+   <td>Standard dashboard interactions</td>
+   <td>Interactive based on the desired workflow</td>
   </tr>
   <tr>
-   <td>Fixed, static layout
-   </td>
-   <td>Dynamic layout determined by logic
-   </td>
+   <td>Fixed, static layout</td>
+   <td>Dynamic layout determined by logic</td>
   </tr>
   <tr>
-   <td>Each element is a tile
-   </td>
-   <td>Elements can be grouped and purposefully-arranged
-   </td>
+   <td>Each element is a tile</td>
+   <td>Elements can be grouped and purposefully-arranged</td>
   </tr>
   <tr>
-   <td>Filters are global
-   </td>
-   <td>Users have preferences and their own defaults
-   </td>
+   <td>Filters are global</td>
+   <td>Users have preferences and their own defaults</td>
   </tr>
   <tr>
-   <td>Minimal software development lifecycle
-   </td>
-   <td>Strong SDLC to promote user trust
-   </td>
+   <td>Minimal software development lifecycle</td>
+   <td>Strong SDLC to promote user trust</td>
   </tr>
   <tr>
-   <td>Look and feel are ignored
-   </td>
-   <td>Custom look and feel to match company products
-   </td>
+   <td>Look and feel are ignored</td>
+   <td>Custom look and feel to match company products</td>
   </tr>
   <tr>
-   <td>Low bar for performance
-   </td>
-   <td>High bar for performance
-   </td>
+   <td>Low bar for performance</td>
+   <td>High bar for performance</td>
   </tr>
 </table>
 

website/blog/2021-12-05-how-to-build-a-mature-dbt-project-from-scratch.md

@@ -85,7 +85,7 @@ The most important thing we’re introducing when your project is an infant is t
 
 * Configure your first [sources](/docs/build/sources)
 
-* Introduce modularity with [{{ ref() }}](/reference/dbt-jinja-functions/ref) and [{{ source() }}](/reference/dbt-jinja-functions/source)
+* Introduce modularity with [\{\{ ref() \}\}](/reference/dbt-jinja-functions/ref) and [\{\{ source() \}\}](/reference/dbt-jinja-functions/source)
 
 * [Document](/docs/build/documentation) and [test](/docs/build/data-tests) your first models
 
@@ -99,9 +99,9 @@ Specifically, now is when it's useful to introduce **_modularity_** to our proje
 
 We’re going to:
 
-* Break out reused code into separate models and use [{{ ](/reference/dbt-jinja-functions/ref)[ref](/reference/dbt-jinja-functions/ref)[() }}](/reference/dbt-jinja-functions/ref) to build dependencies
+* Break out reused code into separate models and use [\{\{ ref() }}](/reference/dbt-jinja-functions/ref) to build dependencies
 
-* Use the[ {{ source() }}](/reference/commands/source) macro to declare our raw data dependencies
+* Use the[ \{\{ source() \}\}](/reference/commands/source) macro to declare our raw data dependencies
 
 * Dip our toes into testing and documenting our models
 

website/blog/2022-06-30-coalesce-sql.md

@@ -5,7 +5,7 @@ slug: coalesce-sql-love-letter
 
 authors: [kira_furuichi]
 
-tags: [SQL Magic]
+tags: [sql magic]
 hide_table_of_contents: false
 
 date: 2022-05-08

website/blog/2022-06-30-extract-sql-function.md

@@ -5,7 +5,7 @@ slug: extract-sql-love-letter
 
 authors: [kira_furuichi]
 
-tags: [SQL Magic]
+tags: [sql magic]
 hide_table_of_contents: false
 
 date: 2022-05-15

website/blog/2022-06-30-lower-sql-function.md

@@ -6,7 +6,7 @@ canonical_url: https://docs.getdbt.com/sql-reference/lower
 
 authors: [kira_furuichi]
 
-tags: [SQL Magic]
+tags: [sql magic]
 hide_table_of_contents: false
 
 date: 2022-05-11

website/blog/2022-07-05-date-trunc-sql-love-letter.md

@@ -57,7 +57,7 @@ date_trunc(<date/time field>, <date part>)
 ```
 
 > **A note on BigQuery:**
-> BigQuery’s DATE_TRUNC function supports the truncation of date types, whereas Snowflake, Redshift, and Databricks’ <date/time field> can be a date or timestamp data type. BigQuery also supports DATETIME_TRUNC and TIMESTAMP_TRUNC functions to support truncation of more granular date/time types.
+> BigQuery’s DATE_TRUNC function supports the truncation of date types, whereas Snowflake, Redshift, and Databricks’ `date/time field` can be a date or timestamp data type. BigQuery also supports DATETIME_TRUNC and TIMESTAMP_TRUNC functions to support truncation of more granular date/time types.
 
 ## A dbt macro to remember
 

website/blog/2022-07-26-configuring-grants.md

@@ -204,6 +204,6 @@ This is just a sample of the issues we've seen:
 - [Post hooks that call macros get parsed with execute = False #2370](https://github.com/dbt-labs/dbt-core/issues/2370)
 - [get_relation returns none in hook context #2938](https://github.com/dbt-labs/dbt-core/issues/2938)
 - [this.is_view and this.is_table not working in BigQuery inside a hook #3529](https://github.com/dbt-labs/dbt-core/issues/3529)
-- [custom table schema path of {{ this }} parsed in correctly in post-hook macro #3985](https://github.com/dbt-labs/dbt-core/issues/3985)
+- [custom table schema path of \{\{ this \}\} parsed in correctly in post-hook macro #3985](https://github.com/dbt-labs/dbt-core/issues/3985)
 - [Post-hook doesn't resolve custom schema #4023](https://github.com/dbt-labs/dbt-core/issues/4023)
 - [[CT-80] [Bug] post-hook macro generates SQL with incorrect source table #4606](https://github.com/dbt-labs/dbt-core/issues/4606)

website/blog/2023-12-15-serverless-free-tier-data-stack-with-dlt-and-dbt-core.md

@@ -63,7 +63,7 @@ When I'm happy with the results, I use the [ready-made dlt Sheets source connect
 
 For transforming I use my favorite solution, dbt Core. For running and orchestrating dbt on Cloud Functions, I am using dlt’s dbt Core runner. The benefit of the runner in this context is that I can re-use the same credential setup, instead of creating a separate profiles.yml file.
 
-This is the package I created: <https://github.com/euanjohnston-dev/idealista_dbt_pipeline>
+This is the package I created: [https://github.com/euanjohnston-dev/idealista_dbt_pipeline](https://github.com/euanjohnston-dev/idealista_dbt_pipeline)
 
 ### Production-readying the pipeline
 

website/blog/categories.yml

@@ -15,9 +15,9 @@
   display_title: dbt tutorials
   description: Best practices in the usage of our favorite data transformation tool.
   is_featured: true    
-- name: SQL magic
+- name: sql magic
   display_title: SQL magic
   description: Stories of dbt developers making SQL sing across warehouses.
   is_featured: true
 - name: dbt Cloud
-  description: Using dbt Cloud to build for scale
+  description: Using dbt Cloud to build for scale