diff --git a/docs/content/concepts/metadata-tags/asset-metadata.mdx b/docs/content/concepts/metadata-tags/asset-metadata.mdx
index 24b8c3741db27..6350350eda3f0 100644
--- a/docs/content/concepts/metadata-tags/asset-metadata.mdx
+++ b/docs/content/concepts/metadata-tags/asset-metadata.mdx
@@ -29,6 +29,7 @@ Dagster supports attaching a few different types of definition metadata:
 - [**Arbitrary metadata**](#arbitrary-metadata-using-the-metadata-parameter), such as the storage location of the table produced by the asset
 - [**Asset owners**](#asset-owners), which are the people and/or teams who own the asset
 - [**Column-level lineage**](#column-level-lineage), which is information about how a column is created and used
+- [**Code references**](#code-references), which link to the source code of the asset locally or in your source control repository
 
 ### Arbitrary metadata using the metadata parameter
 
@@ -83,6 +84,10 @@ from dagster import asset
 def leads(): ...
 ```
 
+### Code references
+
+Attaching code references to an asset definition allows you to easily navigate to the asset's source code, either locally in your editor or in your source control repository. For more information, refer to the [Code references guide](/guides/dagster/code-references).
+
 ---
 
 ## Attaching materialization metadata