From 116b6fde9c937fce4bf8595a73a3329feb37d596 Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Tue, 24 Dec 2024 15:24:53 +0000
Subject: [PATCH] Update website/docs/guides/duckdb-qs.md

---
 website/docs/guides/duckdb-qs.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/website/docs/guides/duckdb-qs.md b/website/docs/guides/duckdb-qs.md
index 63fe1ed194..e5e5f97d6f 100644
--- a/website/docs/guides/duckdb-qs.md
+++ b/website/docs/guides/duckdb-qs.md
@@ -267,7 +267,11 @@ Additionally, with your new understanding of the basics of using dbt Core with D
 
 ### Document your project
 
+To document your dbt projects with DuckDB, follow the steps:
 
+- Use the `dbt docs generate` command to compile information about your dbt project and warehouse into `manifest.json` and `catalog.json` files
+- Run the [`dbt docs serve`](/reference/commands/cmd-docs#dbt-docs-serve) command to create a local website using the generated `.json` files. This allows you to view your project's documentation in a web browser.
+- Enhance your documentation by adding [descriptions](/reference/resource-properties/description) to models, columns, and sources using the `description` key in your YAML files.
 
 ### Commit your changes