a little more

Signed-off-by: bmorelli25 <[email protected]>

Author: bmorelli25

docs/configure/site/content.md

@@ -17,18 +17,55 @@ This section defines different build environments for the documentation site.
 
 Each environment specifies configuration details such as the site URI, content source, path prefix, Google Tag Manager settings, and feature flags.
 
+Example:
+
+```yml
+environments:
+  prod:
+    uri: https://www.elastic.co
+    path_prefix: docs
+    content_source: current
+    allow_indexing: true
+    google_tag_manager:
+      enabled: true
+      id: GTM-KNJMG2M
+```
+
 ## `shared_configuration`
 
-This section defines YAML anchors for common settings shared among multiple repositories.
+This section defines YAML anchors for common settings shared among multiple repositories and deployment environments.
+
+The following example sets a unique `stack` version for each of the three defined deployment environments:
+
+```yml
+  stack: &stack
+    current:  9.0
+    next: 9.1
+    edge: main
+```
 
 ## `narrative`
 
 Configures the main `docs-content` repository.
 
+Example:
+
+```yml
+narrative:
+  checkout_strategy: full
+```
+
 ## `references`
 
 Configures all other repositories whose docs content should be included or referenced in the build. Each can have custom settings for branch, checkout method, etc.
 
+Example:
+
+```yml
+references:
+  apm-server:
+```
+
 ### Branching strategy
 
 How you add a reference repository depends on its [branching strategy](../content-sources.md#branching-strategies).

docs/configure/site/legacy-url-mappings.md

@@ -1,8 +1,12 @@
 # Legacy URL mappings
 
-This [`legacy-url-mappings.yml`](https://github.com/elastic/docs-builder/blob/main/config/legacy-url-mappings.yml) file manages legacy URL patterns for Elastic documentation, mapping the path of each legacy build URL to a list of documentation versions.
+This [`legacy-url-mappings.yml`](https://github.com/elastic/docs-builder/blob/main/config/legacy-url-mappings.yml) file manages legacy URL patterns for Elastic documentation, mapping the path of each legacy build URL to a list of documentation versions. It ensures that users can easily find previous versions of our documentation.
 
-It ensures that users can easily find previous versions of our documentation.
+This example maps documentation that references `elastic.co/guide/en/elasticsearch/reference/ to Elastic Stack versioned URL paths:
+
+```yml
+en/elasticsearch/reference/: *stack
+```
 
 ## Structure
 
@@ -18,6 +22,3 @@ The first version in the `mappings` list is treated as the "current" version in
 
 ## Example entry
 
-```yml
-en/elasticsearch/reference/: *stack
-```

docs/configure/site/navigation.md

@@ -2,6 +2,17 @@
 
 The [`navigation.yml`](https://github.com/elastic/docs-builder/blob/main/config/navigation.yml) file acts as a global navigation index. Each entry points to a `toc.yml` file, which contains the navigation tree for that section. This design allows each section/project/team to manage its own navigation independently of other content sets.
 
+Example:
+
+```yml
+toc:
+  - toc: get-started # No toc.yml indicates a docs-content directory
+  - toc: extend
+    children:
+      - toc: kibana://extend # A toc.yml file in the Kibana repo at docs/extend
+        path_prefix: extend/kibana # The URL path for built content will be elastic.co/docs/extend/kibana/FILE_PATH+NAME
+```
+
 ## `toc`
 
 The location of the table of contents file.

docs/configure/site/versions.md

@@ -1,6 +1,17 @@
 # `versions.yml`
 
-The [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml) file specifies which versions of each product should be recognized as the minimum (base) and the latest (current) in documentation builds. These versions are surfaced to the user via `applies_to` tags.
+The [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml) file specifies which versions of each product should be recognized as the minimum (base) and the latest (current) in documentation builds.
+
+This example sets the Elastic Stack base and current versions while also assigning them to a variable that can be accessed with `*stack`
+
+```yml
+versioning_systems:
+  stack: &stack
+    base: 9.0
+    current: 9.0.4
+```
+
+Versions set in this file are surfaced to the user via `applies_to` tags.
 
 :::{include} /contribute/_snippets/tag-processing.md
 :::