[docs] - Add Declarative Automation concept page (DOC-321)

docs/content/_navigation.json

@@ -170,8 +170,8 @@
             "path": "/concepts/partitions-schedules-sensors/sensors"
           },
           {
-            "title": "Auto-materialization policies",
-            "path": "/concepts/assets/asset-auto-execution"
+            "title": "Declarative Automation (Experimental)",
+            "path": "/concepts/automation/declarative-automation"
           },
           {
             "title": "Asset Sensors",

docs/content/concepts.mdx

@@ -67,8 +67,8 @@ Dagster offers several ways to run data pipelines without manual intervention, i
     href="/concepts/partitions-schedules-sensors/sensors"
   ></ArticleListItem>
   <ArticleListItem
-    title="Auto-materialize policies"
-    href="/concepts/assets/asset-auto-execution"
+    title="Declarative Automation"
+    href="/concepts/automation/declarative-automation"
   ></ArticleListItem>
   <ArticleListItem
     title="Asset Sensors"

docs/content/concepts/automation.mdx

@@ -41,18 +41,16 @@ You can use sensors to run a job or materialize an asset in response to specific
 
 You can also use sensors to act on the status of a job run. Refer to the [Sensors documentation][sensors] to learn more.
 
-### Auto-materialize policies <Experimental />
+### Declarative Automation <Experimental />
 
-If you want a declarative approach to automating your pipelines, Auto-materialize policies (AMP) may be a good fit. AMPs allow you to assign policies to assets and let Dagster determine the best approach to keeping assets up-to-date while adhering to those policies.
+Declarative Automation allows you to automatically materialize assets when specified criteria are met. Using Declarative Automation, you could update assets:
 
-For example, with AMPs, you can update assets based on:
+- When the asset hasn't yet been materialized
+- When an asset's upstream dependency has been updated
+- After an asset's parents have been updated since a cron tick
+- ... based on your own custom conditions
 
-- Whether an upstream dependency has been updated
-- Whether an upstream dependency has the latest data from its dependencies
-- Whether a materialization has occured since the last tick of a cron schedule
-- ... and more
-
-AMPs are declared on an asset-by-asset basis, but can be applied to multiple assets at once. Refer to the [Auto-materializing Assets documentation][auto-materialize-policies] to learn more.
+Materialization conditions are declared on an asset-by-asset basis. Refer to the [Declarative Automation documentation][declarative-automation] to learn more.
 
 ### Asset Sensors <Experimental />
 
@@ -83,7 +81,7 @@ The following cheatsheet contains high-level details about each of the automatio
     <tr>
       <th
         style={{
-          width: "20%",
+          width: "15%",
         }}
       >
         Method
@@ -175,13 +173,13 @@ The following cheatsheet contains high-level details about each of the automatio
     </tr>
     <tr>
       <td>
-        <a href="/concepts/assets/asset-auto-execution">
-          Auto-materialize policies
+        <a href="/concepts/automation/declarative-automation">
+          Declarative Automation
         </a>
       </td>
       <td>
-        Automatically materializes an asset or selection of assets when
-        specified criteria (ex: upstream changes) are met
+        Automatically materializes an asset when specified criteria (ex:
+        upstream changes) are met
       </td>
       <td>
         <ul
@@ -251,4 +249,4 @@ The following cheatsheet contains high-level details about each of the automatio
 
 [asset-sensors]: /concepts/partitions-schedules-sensors/asset-sensors
 
-[auto-materialize-policies]: /concepts/assets/asset-auto-execution
+[declarative-automation]: /concepts/automation/declarative-automation