Updated doc to show new way of defining snapshots

website/docs/reference/snapshot-properties.md

@@ -41,3 +41,40 @@ snapshots:
 
 ```
 </File>
+
+<VersionBlock firstVersion="1.9">
+
+## Define snapshots in YAML
+
+Defining a snapshot in YAML treats snapshots as a distinct resource type, separate from models, allowing for improved organization and consistency within your code.
+
+They don't contain logic, similar to exposures, sources, and tests. To add extra logic to your snapshot, you can break it out into an ephemeral model for cleaner development and testing, and then create a snapshot of that model.
+
+<File name='snapshots/<filename>.yml'>
+
+```yml
+
+# snapshots/my_snapshots.yml
+snapshots:
+  - name: orders_snapshot
+    relation: source('jaffle_shop', 'orders')
+    config:
+      schema: snapshots
+      database: analytics
+      unique_key: id
+      strategy: timestamp
+      updated_at: updated_at
+
+```
+
+</File>
+In this example, the snapshot configuration tracks changes to the orders table over time. The transformation in this snapshot is:  `select * from {{ source('jaffle_shop', 'orders') }}`.
+### Exceptions
+- Best practice: snapshot an ephemeral model that contains the logic.
+  -  Create a "staging" layer on top of your snapshots for cleanup (this could even be an ephemeral model if you don’t want clutter in your warehouse).
+
+This approach also speeds up development, as it lets you run the query directly without needing to run the snapshot every time.
+
+
+</VersionBlock>
+