Add code callouts attribute and replace code-callout shortcodes (#7069)

* feat(layouts): add callout and callout-color code fence attributes

  Support highlighting code in code blocks via fence attributes instead of
  the code-callout shortcode. Defaults to green when callout-color is omitted.
  Works alongside placeholders on the same code block.

* docs: update code callouts docs with fence attribute syntax

  Document the new callout and callout-color code fence attributes as the
  preferred approach. Move the shortcode syntax to a backward-compatibility
  note.

* feat(callouts): add new callout attribute, replace and remove code-callout shortcode

Author: sanderson

DOCS-SHORTCODES.md

@@ -146,7 +146,7 @@ Use the `{{< api-endpoint >}}` shortcode to generate a code block that contains
 - **method**: HTTP request method (get, post, patch, put, or delete)
 - **endpoint**: API endpoint
 - **api-ref**: Link the endpoint to a specific place in the API documentation
-- **influxdb_host**: Specify which InfluxDB product host to use *if the `endpoint` contains the `influxdb/host` shortcode*. Uses the current InfluxDB product as default. Supports the following product values:
+- **influxdb\_host**: Specify which InfluxDB product host to use *if the `endpoint` contains the `influxdb/host` shortcode*. Uses the current InfluxDB product as default. Supports the following product values:
   - oss
   - cloud
   - serverless
@@ -737,16 +737,32 @@ InfluxDB 3 Enterprise and InfluxDB 3 Core support different kinds of tokens. The
 
 ### Code callouts
 
-Use the `{{< code-callout >}}` shortcode to highlight and emphasize a specific piece of code (for example, a variable, placeholder, or value) in a code block. Provide the string to highlight in the code block. Include a syntax for the codeblock to properly style the called out code.
+Use the `callout` code fence attribute to highlight and emphasize specific code (for example, a variable, placeholder, or value) in a code block.
+Provide a regular expression pattern to match the text to highlight.
+Use the optional `callout-color` attribute to specify the highlight color (defaults to `green`).
 
-````md
-{{< code-callout "03a2bbf46249a000" >}}
+**Available colors:** `green` (default), `magenta`, `orange`, `delete`/`strike`
 
-```sh
+````md
+```sh { callout="03a2bbf46249a000" }
 http://localhost:8086/orgs/03a2bbf46249a000/...
 ```
+````
+
+With an explicit color:
+
+````md
+```sh { callout="--host" callout-color="orange" }
+influx query --host http://localhost:8086
+```
+````
 
-{{< /code-callout >}}
+You can use both `callout` and `placeholders` attributes on the same code block:
+
+````md
+```sh { placeholders="DATABASE_NAME" callout="--host" callout-color="magenta" }
+influx query --host http://localhost:8086 --database DATABASE_NAME
+```
 ````
 
 ### Placeholders in code samples

content/influxdb/cloud/admin/organizations/view-orgs.md

@@ -35,11 +35,9 @@ Use the InfluxDB UI or `influx` CLI to view your organization ID.
 
 After logging in to the InfluxDB UI, your organization ID appears in the URL.
 
-{{< code-callout "03a2bbf46249a000" >}}
-```sh
+```sh { callout="03a2bbf46249a000" }
 https://cloud2.influxdata.com/orgs/03a2bbf46249a000/...
 ```
-{{< /code-callout >}}
 
 ### Organization ID in the CLI
 

content/influxdb/cloud/reference/regions.md

@@ -20,20 +20,16 @@ Use the URLs below to interact with your InfluxDB Cloud instances with the
 
 <a href="https://www.influxdata.com/influxdb-cloud-2-0-provider-region/" target="_blank" class="btn">Request a cloud region</a>
 
-{{% note %}}
-#### Regions with multiple clusters
-
-Some InfluxDB Cloud regions have multiple Cloud clusters, each with a unique URL.
-To find your cluster URL, [log in to your InfluxDB Cloud organization](https://cloud2.influxdata.com)
-and review your organization URL. The first subdomain identifies your 
-InfluxDB Cloud cluster. For example:
-
-{{< code-callout "us-west-2-1" >}}
-```sh
-https://us-west-2-1.aws.cloud2.influxdata.com/orgs/03a2bbf46249a000/...
-```
-{{< /code-callout >}}
-
-{{% /note %}}
+> [!Note]
+> #### Regions with multiple clusters
+> 
+> Some InfluxDB Cloud regions have multiple Cloud clusters, each with a unique URL.
+> To find your cluster URL, [log in to your InfluxDB Cloud organization](https://cloud2.influxdata.> com)
+> and review your organization URL. The first subdomain identifies your 
+> InfluxDB Cloud cluster. For example:
+> 
+> ```sh { callout="us-west-2-1" }
+> https://us-west-2-1.aws.cloud2.influxdata.com/orgs/03a2bbf46249a000/...
+> ```
 
 {{< cloud_regions >}}

content/influxdb/cloud/visualize-data/dashboards/_index.md

@@ -22,11 +22,9 @@ Use the InfluxDB UI or `influx` CLI to view your dashboard ID.
 
 When viewing a dashboard in the InfluxDB UI, your dashboard ID appears in the URL.
 
-{{< code-callout "04b6b15034cc000" >}}
-```sh
+```sh { callout="04b6b15034cc000" }
 https://cloud2.influxdata.com/orgs/03a2bbf46249a000/dashboards/04b6b15034cc000/...
 ```
-{{< /code-callout >}}
 
 ### Dashboard ID in the CLI
 Use [`influx dashboards`](/influxdb/cloud/reference/cli/influx/dashboards/) to view a list of dashboards and IDs.

content/influxdb/v1/administration/backup_and_restore.md

@@ -100,15 +100,13 @@ the legacy format.
 To create or restore from a backup or in the portable format, include the
 `-portable` flag with your backup command.
 
-{{< code-callout "-portable" >}}
-```sh
+```sh { callout="-portable" }
 # Create a backup in the portable format
 influxd backup -portable /path/to/backup-destination
 
 # Restore from a portable backup
 influxd restore -portable /path/to/backup-destination
 ```
-{{< /code-callout >}}
 
 ### Determine your backup's format
 Use the directory structure of the backup directory to determine the format of the backup.

content/influxdb/v2/admin/organizations/view-orgs.md

@@ -46,13 +46,9 @@ Use the InfluxDB UI or `influx` CLI to view your organization ID.
 ### Organization ID in the UI
 
 After logging in to the InfluxDB UI, your organization ID appears in the URL.
-
-{{< code-callout "03a2bbf46249a000" >}}
-```sh
+```sh { callout="03a2bbf46249a000" }
 http://localhost:8086/orgs/03a2bbf46249a000/...
 ```
-{{< /code-callout >}}
-
 
 ### Organization ID in the CLI
 

content/influxdb/v2/visualize-data/dashboards/_index.md

@@ -21,12 +21,9 @@ Use the InfluxDB UI or `influx` CLI to view your dashboard ID.
 ### Dashboard ID in the UI
 
 When viewing a dashboard in the InfluxDB UI, your dashboard ID appears in the URL.
-
-{{< code-callout "04b6b15034cc000" >}}
-```sh
+```sh { callout="04b6b15034cc000" }
 http://localhost:8086/orgs/03a2bbf46249a000/dashboards/04b6b15034cc000/...
 ```
-{{< /code-callout >}}
 
 ### Dashboard ID in the CLI
 Use [`influx dashboards`](/influxdb/v2/reference/cli/influx/dashboards/) to view a list of dashboards and IDs.

content/influxdb3/cloud-dedicated/process-data/visualize/superset.md

@@ -226,17 +226,13 @@ With Superset running, you're ready to [log in](#log-in-to-superset) and set up
     - **`?database`**: URL-encoded InfluxDB [database name](/influxdb3/cloud-dedicated/admin/databases/list/)
     - **`?token`**: InfluxDB [API token](/influxdb3/cloud-dedicated/get-started/setup/) with `READ` access to the specified database
 
-    {{< code-callout "&lt;(domain|port|database-name|token)&gt;" >}}
-{{< code-callout "cluster-id\.influxdb\.io|443|example-database|example-token" >}}
-```sh
-# Syntax
-datafusion+flightsql://<domain>:<port>?database=<database-name>&token=<token>
+    ```sh { callout = "(&lt;(domain|port|database-name|token)&gt;)|cluster-id\.influxdb\.io|443|example-database|example-token"}
+    # Syntax
+    datafusion+flightsql://<domain>:<port>?database=<database-name>&token=<token>
 
-# Example
-datafusion+flightsql://{{< influxdb/host >}}:443?database=example-database&token=example-token
-```
-{{< /code-callout >}}
-    {{< /code-callout >}}
+    # Example
+    datafusion+flightsql://{{< influxdb/host >}}:443?database=example-database&token=example-token
+    ```
 
 6.  Click **Test Connection** to ensure the connection works.
 7.  Click **Connect** to save the database connection.

content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python.md

@@ -188,12 +188,9 @@ to install a recent version of the Python programming language for your system.
     {{< /tabs-wrapper >}}
 
 When a virtual environment is activated, the name displays at the beginning of your terminal command line--for example:
-  
-{{% code-callout "(virtualenv-1)"%}}
-```sh
+```sh { callout="(virtualenv-1)" }
 (virtualenv-1) $ PROJECT_DIRECTORY
 ```
-{{% /code-callout %}}
 
 ## Query InfluxDB
 
@@ -263,9 +260,7 @@ If using a non-POSIX-compliant operating system (such as Windows), specify the r
 
 The following example shows how to use the Python `certifi` package and client library options to pass the certificate path:
 
-{{% code-placeholders "DATABASE_(NAME|TOKEN)" %}}
-{{< code-callout "flight_client_options|tls_root_certs|(cert\b)" >}}
-```py
+```py { placeholders="DATABASE_(NAME|TOKEN)" callout="flight_client_options|tls_root_certs|(cert\b)" }
 from influxdb_client_3 import InfluxDBClient3, flight_client_options
 import certifi
 
@@ -282,8 +277,6 @@ flight_client_options=flight_client_options(
 tls_root_certs=cert))
 ...
 ```
-{{< /code-callout >}}
-{{% /code-placeholders %}}
 
 For more information, see [`influxdb_client_3` query exceptions](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/#query-exceptions).
 

content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/analyze-query-plan.md

@@ -200,16 +200,12 @@ The following steps summarize the [physical plan execution and data flow](#physi
 
 If your table doesn't contain data for the time range in your query, the physical plan starts with an `EmptyExec` leaf node--for example:
 
-{{% code-callout "EmptyExec"%}}
-
-```sql
+```sql { callout="EmptyExec" }
 ProjectionExec: expr=[temp@0 as temp]
     SortExec: expr=[time@1 ASC NULLS LAST]
         EmptyExec: produce_one_row=false
 ```
 
-{{% /code-callout %}}
-
 ## Analyze a query plan for leading edge data
 
 The following sections guide you through analyzing a physical query plan for a typical time series use case--aggregating recently written (_leading edge_) data.
@@ -621,14 +617,10 @@ The remaining ParquetExec_B expressions are similar to those in [ParquetExec_A](
 
 If you compare [`file_group`](#file_groups) paths in [ParquetExec_A](#parquetexec_a) to those in [ParquetExec_B](#parquetexec_b), you'll notice that both contain files from the same partition:
 
-{{% code-callout "b862a7e9b329ee6a4..." %}}
-
-```text
+```text { callout="b862a7e9b329ee6a4..." }
 1/1/b862a7e9b329ee6a4.../...
 ```
 
-{{% /code-callout %}}
-
 The planner may distribute files from the same partition to different scan nodes for several reasons, including optimizations for handling [overlaps](#how-a-query-plan-distributes-data-for-scanning)--for example:
 
 - to separate non-overlapped files from overlapped files to minimize work required for deduplication (which is the case in this example)