add config descriptions per user feedback

website/docs/reference/model-configs.md

@@ -3,13 +3,18 @@ title: Model configurations
 description: "Read this guide to understand model configurations in dbt."
 ---
 
+import ConfigResource from '/snippets/_config-description-resource.md';
+import ConfigGeneral from '/snippets/_config-description-general.md';
+
 ## Related documentation
 * [Models](/docs/build/models)
 * [`run` command](/reference/commands/run)
 
 ## Available configurations
 ### Model-specific configurations
 
+<ConfigResource />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"
@@ -78,6 +83,8 @@ models:
 
 ### General configurations
 
+<ConfigGeneral />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"

website/docs/reference/seed-configs.md

@@ -3,9 +3,15 @@ title: Seed configurations
 description: "Read this guide to learn about using seed configurations in dbt."
 ---
 
+import ConfigResource from '/snippets/_config-description-resource.md';
+import ConfigGeneral from '/snippets/_config-description-general.md';
+
+
 ## Available configurations
 ### Seed-specific configurations
 
+<ConfigResource />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"
@@ -56,6 +62,8 @@ seeds:
 
 ### General configurations
 
+<ConfigGeneral />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"

website/docs/reference/snapshot-configs.md

@@ -2,6 +2,11 @@
 title: Snapshot configurations
 description: "Read this guide to learn about using snapshot configurations in dbt."
 ---
+
+import ConfigResource from '/snippets/_config-description-resource.md';
+import ConfigGeneral from '/snippets/_config-description-general.md';
+
+
 ## Related documentation
 * [Snapshots](/docs/build/snapshots)
 * The `dbt snapshot` [command](/reference/commands/snapshot)
@@ -15,6 +20,8 @@ Parts of a snapshot:
 ## Available configurations
 ### Snapshot-specific configurations
 
+<ConfigResource />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"
@@ -95,6 +102,8 @@ snapshots:
 
 ### General configurations
 
+<ConfigGeneral />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"

website/docs/reference/source-configs.md

@@ -4,12 +4,16 @@ description: "Learn how to use source configurations in dbt."
 id: source-configs
 ---
 
+import ConfigGeneral from '/snippets/_config-description-general.md';
+
 ## Available configurations
 
 Sources only support one configuration, [`enabled`](/reference/resource-configs/enabled).
 
 ### General configurations
 
+<ConfigGeneral />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"

website/docs/reference/test-configs.md

@@ -2,6 +2,9 @@
 title: Test configurations
 description: "Read this guide to learn about using test configurations in dbt."
 ---
+import ConfigResource from '/snippets/_config-description-resource.md';
+import ConfigGeneral from '/snippets/_config-description-general.md';
+
 
 ## Related documentation
 
@@ -20,6 +23,8 @@ Click the link on each configuration option to read more about what it can do.
 
 ### Test-specific configurations
 
+<ConfigResource />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"
@@ -114,6 +119,8 @@ This configuration mechanism is supported for specific instances of generic test
 
 ### General configurations
 
+<ConfigGeneral />
+
 <Tabs
   groupId="config-languages"
   defaultValue="project-yaml"

website/snippets/_config-description-general.md

@@ -0,0 +1 @@
+General configurations provide broader operational settings applicable across multiple resource types. Like resource-specific configurations, these can also be set in the project file, property files, or within resource-specific files.

website/snippets/_config-description-resource.md

@@ -0,0 +1 @@
+Resource-specific configurations are applicable to only one dbt resource type rather than multiple resource types. You can define these settings in the project file (`dbt_project.yml`), a property file (`models/properties.yml` for models, similarly for other resources), or within the resource’s file using the `{{ config() }}` macro.