Merge pull request #160 from DataRecce/feature/drc-1097-cll-doc-site

Add the column-level lineage content

Author: popcornylu

docs/assets/images/features/cll-1.png

@@ -2,7 +2,6 @@
 title: Breaking Change Analysis
 icon: octicons/diff-modified-24
 ---
-`Experimental Feature`
 
 Breaking change analysis examines models for modifications to the SQL semantic tree that could potentially alter the data generated by the model, resulting in downstream impact.
 

docs/assets/images/features/cll-2.png

@@ -0,0 +1,39 @@
+---
+title: Column-Level Lineage
+icon: material/file-tree
+---
+
+Column-Level Lineage provides visibility into the upstream and downstream relationships of a column. 
+
+Common use-cases for column-level lineage are
+
+1. **Source Exploration**: During development, column-level lineage helps you understand how a column is derived.
+2. **Impact Analysis**: When modifying the logic of a column, column-level lineage enables you to assess the potential impact across the entire DAG.
+3. **Root Cause Analysis**: Column-level lineage helps identify the possible source of errors by tracing data lineage at the column level.
+
+## Usage
+
+1. Select a node in the lineage DAG, then click the **eye** icon next to the column you want to view.
+
+    ![alt text](../../assets/images/features/cll-1.png){: .shadow}
+
+1. The column-level lineage for the selected column will be displayed.
+
+    ![alt text](../../assets/images/features/cll-2.png){: .shadow}
+
+## Transformation Types
+
+The transformation type is also displayed for each column, which will help you understand how the column was generated or modified.
+
+| Type | Description  |
+|------|--------------|
+| Pass-through  |The column is directly selected from the upstream table. |
+| Renamed | The column is selected from the upstream table but with a different name. |
+| Derived | The column is created through transformations applied to upstream columns, such as calculations, conditions, functions, or aggregations. |
+| Source | The column is not derived from any upstream data. It may originate from a seed/source node, literal value, or data generation function. |
+| Unknown | We have no information about the transformation type. This could be due to a parse error, or other unknown reason. | 
+
+
+## Limitation
+
+Column-level lineage only displays column selection operations. It does not indicate if a column has been used in filters (WHERE clauses), with grouping (GROUP BY), joins, or other transformations.

docs/docs/features/breaking-change-analysis.md

@@ -55,6 +55,7 @@ nav:
           - docs/features/preset-checks.md
           - docs/features/node-selection.md
           - docs/features/breaking-change-analysis.md
+          - docs/features/column-level-lineage.md
           - docs/reference/configuration.md
       - Scenarios:
           - docs/guides/scenario-dev.md