more

Author: shainaraskas

docs/contribute/_snippets/tag-processing.md

@@ -1,6 +1,6 @@
 `applies_to` tags are rendered as badges in the documentation output. They reproduce the "key + lifecycle status + version" indicated in the content sources.
 
-Specifically for versioned products, badges will display differently when the applies_to key specifies a product version that has not been released to our customers yet.
+Specifically for versioned products, badges will display differently when the `applies_to` key specifies a product version that has not been released to our customers yet.
 
 * `Planned` (if the lifecycle is preview, beta, or ga)
 * `Deprecation planned` (if the lifecycle is deprecated)
@@ -14,4 +14,4 @@ When multiple lifecycle statuses and versions are specified in the sources, seve
 Visuals and wording in the output documentation are subject to changes and optimizations.
 :::
 
-% todo: link
+% todo: link to central config

docs/contribute/cumulative-docs.md

@@ -1,5 +1,9 @@
 # Write cumulative documentation 
 
+<!--
+This page explains our cumulative documentation philosophy, paired with examples. Component guidance for reference purposes goes in syntax/applies.md. 
+-->
+
 In our markdown-based documentation system, we write docs cumulatively regardless of the [deployment model](deployment-models.md) selected.
 
 **What does this mean?** 

docs/syntax/_snippets/section-level-applies-examples.md

@@ -1,6 +1,6 @@
 * The whole page is generally applicable to {{stack}} 9.0 and to {{serverless-short}}, but one specific section isn’t applicable to {{serverless-short}} (and there is no alternative for it):
 
-    ````markdown
+    ````md
     --- 
     applies_to:
       stack: ga

docs/syntax/applies.md

@@ -1,5 +1,10 @@
 # Applies to
 
+<!--
+This page explains concrete usage of the applies_to tag. Cumulative authoring philosophy and guidance goes in contribute/cumulative-docs.md. 
+-->
+
+
 Starting with Elastic Stack 9.0, ECE 4.0, and ECK 3.0, documentation follows a [cumulative approach](../contribute/cumulative-docs.md): instead of creating separate pages for each product and release, we update a single page with product- and version-specific details over time.
 
 To support this, source files use a tagging system to indicate:
@@ -8,6 +13,11 @@ To support this, source files use a tagging system to indicate:
 
 This is what the `applies_to` metadata is for. It can be used at the page, section, or inline level to specify applicability with precision.
 
+## `applies_to` tags in the output
+
+:::{include} /contribute/_snippets/tag-processing.md
+:::
+
 ## When and where to use `applies_to`
 
 The `applies_to` metadata can be added at different levels in the documentation:
@@ -30,6 +40,8 @@ The `applies_to` metadata can be added at different levels in the documentation:
 
 ❌ If the product is not versioned (meaning all users are always on the latest version, like in serverless or cloud), you do not need to tag a new GA feature.
 
+For detailed guidance, refer to [](/contribute/cumulative-docs.md).
+
 ## Syntax
 
 The `applies_to` metadata supports an [exhaustive list of keys](#structured-model).