diff --git a/doc/.vale/gitlab_docs/AlertBoxStyle.yml b/doc/.vale/gitlab_docs/AlertBoxStyle.yml
index 55f6ba85824ba897457f8c05f54217f2c339b603..abb3b6f2485104f2ffe6dd564154b6a8b9efc3c1 100644
--- a/doc/.vale/gitlab_docs/AlertBoxStyle.yml
+++ b/doc/.vale/gitlab_docs/AlertBoxStyle.yml
@@ -13,4 +13,4 @@ level: error
 nonword: true
 scope: raw
 tokens:
-  - '^ *(> )?\**(note|tip|caution|danger|warning|flag|disclaimer|details|history)\**:\**$'
+  - '^ *(> )?(- )?\**(note|tip|caution|danger|warning|flag|disclaimer|details|history)\**:\**$'
diff --git a/doc/.vale/gitlab_docs/HistoryItems.yml b/doc/.vale/gitlab_docs/HistoryItems.yml
index 21274658084a4d2fb1beaf850a0359be2fcc27d7..c3028b3ee23a8ad801f1a63abe7e91085e2f59c9 100644
--- a/doc/.vale/gitlab_docs/HistoryItems.yml
+++ b/doc/.vale/gitlab_docs/HistoryItems.yml
@@ -4,12 +4,12 @@
 # Ensures history items are properly formatted.
 #
 extends: existence
-message: "History items must always start with '> -', one item per line, even if there is only one item."
+message: "History items must always use Hugo shortcodes and be a list with each line starting with '-', one item per line, even if there is only one item."
 link: https://docs.gitlab.com/development/documentation/feature_flags/#add-history-text
 vocab: false
 level: error
 nonword: true
 scope: raw
 tokens:
-  - '(?<=^#+[^\n]*\n\n)> [^-]'
-  - '^> - [^\n]*\n[^\n>`]'
+  - '\{\{< history >\}\}\n\n[^-]'
+  - '(^#+[^\n]*|\{\{< /details >\}\})\n\n> -'
diff --git a/doc/.vale/gitlab_docs/HistoryItemsOrder.yml b/doc/.vale/gitlab_docs/HistoryItemsOrder.yml
index b121017b82a7bffc3b6c2fd0d9944e5b0f3eb94a..b8d938a55b01191753155fad1b1c852451f356a7 100644
--- a/doc/.vale/gitlab_docs/HistoryItemsOrder.yml
+++ b/doc/.vale/gitlab_docs/HistoryItemsOrder.yml
@@ -11,4 +11,4 @@ level: error
 nonword: true
 scope: raw
 tokens:
-  - '^\>[^\n]*\n\nDETAILS'
+  - '\{\{< /history >\}\}\n\n?\{\{< details >\}\}'
diff --git a/doc/administration/cicd/job_logs.md b/doc/administration/cicd/job_logs.md
index c8a6e94d92ebf173f96d84af2799c544f756c144..552330e270cd1d26192a86c26b1ab33ff5aa7375 100644
--- a/doc/administration/cicd/job_logs.md
+++ b/doc/administration/cicd/job_logs.md
@@ -234,13 +234,13 @@ For more information, see how to
 
 ## Incremental logging architecture
 
-> - To use in your instance, ask a GitLab administrator to [enable it](#enable-or-disable-incremental-logging).
-
 By default, job logs are sent from the GitLab Runner in chunks and cached
 temporarily on disk. After the job completes, a background job archives the job
 log. The log is moved to the artifacts directory by default, or to object
 storage if configured.
 
+To use in your instance, ask a GitLab administrator to [enable it](#enable-or-disable-incremental-logging).
+
 In a [scaled-out architecture](../reference_architectures/_index.md) with Rails and
 Sidekiq running on more than one server, these two locations on the file system
 have to be shared using NFS, which is not recommended. Instead:
diff --git a/doc/administration/integration/terminal.md b/doc/administration/integration/terminal.md
index 68947f33d02057844830b000eb95b7a3ab57f500..66d8dcd3079442ff0959121f8543ccc0dc98ecab 100644
--- a/doc/administration/integration/terminal.md
+++ b/doc/administration/integration/terminal.md
@@ -12,7 +12,11 @@ title: Web terminals (deprecated)
 
 {{< /details >}}
 
-> - [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+{{< history >}}
+
+- [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+
+{{< /history >}}
 
 {{< alert type="warning" >}}
 
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md
index c007326879b5f290e66558aa84109f7d36338ca2..85803427caf8621b279d58f09ec16f101affd6d6 100644
--- a/doc/administration/packages/container_registry.md
+++ b/doc/administration/packages/container_registry.md
@@ -1194,7 +1194,11 @@ end
 
 {{< /details >}}
 
-> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/423459) in GitLab 17.3.
+{{< history >}}
+
+- [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/423459) in GitLab 17.3.
+
+{{< /history >}}
 
 The metadata database enables many new registry features, including
 online garbage collection, and increases the efficiency of many registry operations.
diff --git a/doc/administration/raketasks/maintenance.md b/doc/administration/raketasks/maintenance.md
index e6e316032b14561e067891f33c10a2a5142a1eb3..8a6c4968ecec52d7b6108096747e70f7dcd2f711 100644
--- a/doc/administration/raketasks/maintenance.md
+++ b/doc/administration/raketasks/maintenance.md
@@ -479,7 +479,11 @@ gitlab-rake gitlab:db:schema_checker:run
 
 ## Check the database for deduplicate CI/CD tags
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/518698) in GitLab 17.10.
+{{< history >}}
+
+- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/518698) in GitLab 17.10.
+
+{{< /history >}}
 
 This Rake task checks the `ci` database for duplicate tags in the `tags` table.
 This issue might affect instances that have undergone multiple major upgrades over an extended period.
diff --git a/doc/administration/settings/rate_limit_on_users_api.md b/doc/administration/settings/rate_limit_on_users_api.md
index 32912b1e18a1141afe0af0fa3b859b0ba7e103ec..227092c915af58caa445daa459d2f5644e3f405c 100644
--- a/doc/administration/settings/rate_limit_on_users_api.md
+++ b/doc/administration/settings/rate_limit_on_users_api.md
@@ -12,8 +12,12 @@ title: Rate limits on Users API
 
 {{< /details >}}
 
-> - Rate limits for Users API [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/452349) in GitLab 17.1 with a [flag](../feature_flags.md) named `rate_limiting_user_endpoints`. Disabled by default.
-> - [Added](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/181054) customizable rate limits in GitLab 17.10.
+{{< history >}}
+
+- Rate limits for Users API [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/452349) in GitLab 17.1 with a [flag](../feature_flags.md) named `rate_limiting_user_endpoints`. Disabled by default.
+- [Added](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/181054) customizable rate limits in GitLab 17.10.
+
+{{< /history >}}
 
 You can configure the per minute rate limit per IP address and per user for requests to the following [Users API](../../api/users.md).
 
diff --git a/doc/api/commits.md b/doc/api/commits.md
index 6b2e0ff5f450d700388617d246fab52517d27d72..1f5eb950b826fccff4deccdf3163d6bf654c073b 100644
--- a/doc/api/commits.md
+++ b/doc/api/commits.md
@@ -706,7 +706,11 @@ The commit status API for use with GitLab.
 
 ### List the statuses of a commit
 
-> - `pipeline_id`, `order_by`, and `sort` fields [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/176142) in GitLab 17.9.
+{{< history >}}
+
+- `pipeline_id`, `order_by`, and `sort` fields [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/176142) in GitLab 17.9.
+
+{{< /history >}}
 
 List the statuses of a commit in a project.
 The pagination parameters `page` and `per_page` can be used to restrict the list of references.
diff --git a/doc/api/group_service_accounts.md b/doc/api/group_service_accounts.md
index 306c63494b08ac4a37e1478ec211e3a9516f1394..2c4ac724781e1f49de062a1780a9f5e3409a5165 100644
--- a/doc/api/group_service_accounts.md
+++ b/doc/api/group_service_accounts.md
@@ -72,9 +72,9 @@ Example response:
 
 {{< history >}}
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/407775) in GitLab 16.1.
-> - Specify a service account user username or name was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144841) in GitLab 16.10.
-> - Specify a service account user email address was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/181456) in GitLab 17.9 [with a flag](../administration/feature_flags.md) named `group_service_account_custom_email`.
+- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/407775) in GitLab 16.1.
+- Specify a service account user username or name was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144841) in GitLab 16.10.
+- Specify a service account user email address was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/181456) in GitLab 17.9 [with a flag](../administration/feature_flags.md) named `group_service_account_custom_email`.
 
 {{< /history >}}
 
diff --git a/doc/api/merge_request_approvals.md b/doc/api/merge_request_approvals.md
index 53addb244659b26eb1f293cf1fce91ff71371420..30f032f6f807851918bff23c382947d5790eefee 100644
--- a/doc/api/merge_request_approvals.md
+++ b/doc/api/merge_request_approvals.md
@@ -277,7 +277,7 @@ Example response:
 
 ## Project approval rules
 
-> - Use the [project approval rules](#get-all-approval-rules-for-project) to access this information.
+Use the [project approval rules](#get-all-approval-rules-for-project) to access this information.
 
 You can request information about a project's approval configuration using the
 following endpoint:
diff --git a/doc/api/packages/debian.md b/doc/api/packages/debian.md
index df682f5df162ac21538c786c2f82bff1b1e9b348..b11fac1f8e927d9e6c1f22a08245a29dca6e529d 100644
--- a/doc/api/packages/debian.md
+++ b/doc/api/packages/debian.md
@@ -12,7 +12,11 @@ title: Debian API
 
 {{< /details >}}
 
-> - [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
+{{< history >}}
+
+- [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
+
+{{< /history >}}
 
 This is the API documentation for [Debian](../../user/packages/debian_repository/_index.md).
 
diff --git a/doc/api/packages/debian_group_distributions.md b/doc/api/packages/debian_group_distributions.md
index 24d38f75e53b795889b787b7b149f457bb906871..c48775f95e009a1e115ad690ed669126c6bff40e 100644
--- a/doc/api/packages/debian_group_distributions.md
+++ b/doc/api/packages/debian_group_distributions.md
@@ -12,7 +12,11 @@ title: Debian group distributions API
 
 {{< /details >}}
 
-> - [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
+{{< history >}}
+
+- [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
+
+{{< /history >}}
 
 This is the reference documentation for the Debian group distributions API. This API is behind a
 feature flag that is disabled by default. To use this API, you must [enable it](#enable-the-debian-group-api).
diff --git a/doc/api/packages/debian_project_distributions.md b/doc/api/packages/debian_project_distributions.md
index b29fa4a0ede8bdae29150d3d51f555f4c6d9402e..93e1f71afe44e77b0b29529d9d7ea636f7d016d4 100644
--- a/doc/api/packages/debian_project_distributions.md
+++ b/doc/api/packages/debian_project_distributions.md
@@ -12,7 +12,11 @@ title: Debian project distributions API
 
 {{< /details >}}
 
-> - [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
+{{< history >}}
+
+- [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
+
+{{< /history >}}
 
 This is the reference documentation for the Debian project distributions API. This API is behind a
 feature flag that is disabled by default. To use this API, you must [enable the Debian API](#enable-the-debian-api).
diff --git a/doc/ci/environments/_index.md b/doc/ci/environments/_index.md
index 693f0dd0d62677584bb409b2b6974f7b71282c59..f2d1c0cf80d89549ef4b3770b683ac2901031cfe 100644
--- a/doc/ci/environments/_index.md
+++ b/doc/ci/environments/_index.md
@@ -740,7 +740,11 @@ To delete an environment:
 
 ## Access an environment for preparation or verification purposes
 
-> - [Updated](https://gitlab.com/gitlab-org/gitlab/-/issues/437133) to reset `auto_stop_in` for `prepare` and `access` actions in GitLab 17.7.
+{{< history >}}
+
+- [Updated](https://gitlab.com/gitlab-org/gitlab/-/issues/437133) to reset `auto_stop_in` for `prepare` and `access` actions in GitLab 17.7.
+
+{{< /history >}}
 
 You can define a job that accesses an environment for various purposes, such as verification or preparation. This
 effectively bypasses deployment creation, so that you can adjust your CD workflow more accurately.
diff --git a/doc/ci/yaml/_index.md b/doc/ci/yaml/_index.md
index 12e470084bdc356a521b909f4871f96bbcbda829..d518467549c0a2b602c2658410dc0c0d7d73a44f 100644
--- a/doc/ci/yaml/_index.md
+++ b/doc/ci/yaml/_index.md
@@ -480,7 +480,11 @@ In this example, if the `INCLUDE_BUILDS` variable is:
 
 #### `include:integrity`
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/178593) in GitLab 17.9.
+{{< history >}}
+
+- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/178593) in GitLab 17.9.
+
+{{< /history >}}
 
 Use `integrity` with `include:remote` to specifiy a SHA256 hash of the included remote file.
 If `integrity` does not match the actual content, the remote file is not processed
diff --git a/doc/development/advanced_search.md b/doc/development/advanced_search.md
index 297e78e0ea9c979da287c343080b6d4050f1cc44..c92f22aea40373ceabc087937845b10c6cd28a46 100644
--- a/doc/development/advanced_search.md
+++ b/doc/development/advanced_search.md
@@ -213,7 +213,6 @@ See [Recommended process for adding a new document type](#recommended-process-fo
 
 ### Create the index
 
-NOTE
 All new indexes must have:
 
 - `project_id` and `namespace_id` fields (if available). One of the fields must be used for routing.
diff --git a/doc/development/database/avoiding_downtime_in_migrations.md b/doc/development/database/avoiding_downtime_in_migrations.md
index 564ac82d3d5bb1a80032b8fdf13b869524cd886b..c0428aeb128b0905690e01eca2ce3df09f7efe64 100644
--- a/doc/development/database/avoiding_downtime_in_migrations.md
+++ b/doc/development/database/avoiding_downtime_in_migrations.md
@@ -498,12 +498,14 @@ class BackfillMergeRequestMetricsForBigintConversion < Gitlab::Database::Migrati
 end
 ```
 
-NOTES:
+{{< alert type="note" >}}
 
 - With [Issue#438124](https://gitlab.com/gitlab-org/gitlab/-/issues/438124) new instances have all ID columns in bigint.
   The list of IDs yet to be converted to bigint in old instances (includes `Gitlab.com` SaaS) is maintained in `db/integer_ids_not_yet_initialized_to_bigint.yml`.
 - Since the schema file already has all IDs in `bigint`, don't push any changes to `db/structure.sql`.
 
+{{< /alert >}}
+
 ### Monitor the background migration
 
 Check how the migration is performing while it's running. Multiple ways to do this are described below.
diff --git a/doc/development/reactive_caching.md b/doc/development/reactive_caching.md
index 3a9874f67cfa76bac66ee4621e7e2a11b67d167f..fcdc34349782d4308d28a945073de86a1a0faad9 100644
--- a/doc/development/reactive_caching.md
+++ b/doc/development/reactive_caching.md
@@ -5,7 +5,7 @@ info: Any user with at least the Maintainer role can merge updates to this conte
 title: Using `ReactiveCaching`
 ---
 
-> - This doc refers to [`reactive_caching.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/models/concerns/reactive_caching.rb).
+This doc refers to [`reactive_caching.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/models/concerns/reactive_caching.rb).
 
 The `ReactiveCaching` concern is used for fetching some data in the background and storing it
 in the Rails cache, keeping it up-to-date for as long as it is being requested. If the
diff --git a/doc/integration/jira/configure.md b/doc/integration/jira/configure.md
index e81e932b32c82beef4c9ad54b34454eef1a240eb..cfc1030ffb54452541e435f5fefbd2030a944bcb 100644
--- a/doc/integration/jira/configure.md
+++ b/doc/integration/jira/configure.md
@@ -12,7 +12,11 @@ title: Jira issues integration
 
 {{< /details >}}
 
-> - Name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to Jira issues integration in GitLab 17.6.
+{{< history >}}
+
+- Name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to Jira issues integration in GitLab 17.6.
+
+{{< /history >}}
 
 The Jira issues integration connects one or more GitLab projects to a Jira instance.
 You can host the Jira instance yourself or in [Jira Cloud](https://www.atlassian.com/migration/assess/why-cloud).
@@ -233,7 +237,11 @@ To copy the API token, select **Copy**.
 
 ## Migrate from Jira Server to Jira Cloud
 
-> - Integration name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to **Jira issues** in GitLab 17.6.
+{{< history >}}
+
+- Integration name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to **Jira issues** in GitLab 17.6.
+
+{{< /history >}}
 
 To migrate from Jira Server to Jira Cloud in GitLab and maintain your Jira issues integration:
 
diff --git a/doc/integration/jira/issues.md b/doc/integration/jira/issues.md
index f494eaba75f322099d3ad9df8162ad68c3d6a5bd..5cf4b012c6863ee1c60f69f7b6aace4917f7d092 100644
--- a/doc/integration/jira/issues.md
+++ b/doc/integration/jira/issues.md
@@ -92,7 +92,11 @@ When you do not configure custom rules, the
 
 ### Define a regex pattern
 
-> - Integration name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to **Jira issues** in GitLab 17.6.
+{{< history >}}
+
+- Integration name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to **Jira issues** in GitLab 17.6.
+
+{{< /history >}}
 
 You can use a regular expression (regex) to match Jira issue keys.
 The regex pattern must follow the [RE2 syntax](https://github.com/google/re2/wiki/Syntax).
@@ -111,7 +115,11 @@ For more information, see the
 
 ### Define a prefix
 
-> - Integration name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to **Jira issues** in GitLab 17.6.
+{{< history >}}
+
+- Integration name [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166555) to **Jira issues** in GitLab 17.6.
+
+{{< /history >}}
 
 You can use a prefix to match Jira issue keys.
 For example, if your Jira issue key is `ALPHA-1` and you define a `JIRA#` prefix,
diff --git a/doc/user/application_security/dast/browser/_index.md b/doc/user/application_security/dast/browser/_index.md
index 71b71831b50eb29ce7983ada1fda8b47f48fddd9..dbcca549779f8e24ab7fa97a33f8dc9320565b48 100644
--- a/doc/user/application_security/dast/browser/_index.md
+++ b/doc/user/application_security/dast/browser/_index.md
@@ -13,7 +13,11 @@ title: DAST browser-based analyzer
 
 {{< /details >}}
 
-> - [Generally available](https://gitlab.com/groups/gitlab-org/-/epics/9023) in GitLab 15.7 (GitLab DAST v3.0.50).
+{{< history >}}
+
+- [Generally available](https://gitlab.com/groups/gitlab-org/-/epics/9023) in GitLab 15.7 (GitLab DAST v3.0.50).
+
+{{< /history >}}
 
 {{< alert type="warning" >}}
 
diff --git a/doc/user/application_security/dast/browser/configuration/enabling_the_analyzer.md b/doc/user/application_security/dast/browser/configuration/enabling_the_analyzer.md
index 0a8197670a02087f0e5ebc0a5060ec9c2d702009..c6473b028abf7252f5d80311c2a228afc3d11a5d 100644
--- a/doc/user/application_security/dast/browser/configuration/enabling_the_analyzer.md
+++ b/doc/user/application_security/dast/browser/configuration/enabling_the_analyzer.md
@@ -18,9 +18,13 @@ and crawls the site using an embedded browser.
 
 ## Create a DAST CI/CD job
 
-> - This template was [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/87183) to DAST_VERSION: 3 in GitLab 15.0.
-> - This template was updated to DAST_VERSION: 4 in GitLab 16.0.
-> - This template was [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/151910) to DAST_VERSION: 5 in GitLab 17.0.
+{{< history >}}
+
+- This template was [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/87183) to DAST_VERSION: 3 in GitLab 15.0.
+- This template was updated to DAST_VERSION: 4 in GitLab 16.0.
+- This template was [updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/151910) to DAST_VERSION: 5 in GitLab 17.0.
+
+{{< /history >}}
 
 To add DAST scanning to your application, use the DAST job defined
 in the GitLab DAST CI/CD template file. Updates to the template are provided with GitLab
diff --git a/doc/user/application_security/dependency_scanning/_index.md b/doc/user/application_security/dependency_scanning/_index.md
index 910a6522d2cd237e0e4c79bcbf65e8600ae3186a..1a179c97871039372781ebc3f078d093d6d3ed96 100644
--- a/doc/user/application_security/dependency_scanning/_index.md
+++ b/doc/user/application_security/dependency_scanning/_index.md
@@ -1043,7 +1043,11 @@ For more details of the dependency scanning report, see:
 
 ### CycloneDX Software Bill of Materials
 
-> - Generally available in GitLab 15.7.
+{{< history >}}
+
+- Generally available in GitLab 15.7.
+
+{{< /history >}}
 
 Dependency Scanning outputs a [CycloneDX](https://cyclonedx.org/) Software Bill of Materials (SBOM)
 for each supported lock or build file it detects.
diff --git a/doc/user/application_security/dependency_scanning/dependency_scanning_sbom/_index.md b/doc/user/application_security/dependency_scanning/dependency_scanning_sbom/_index.md
index 9fb6b57ef6f447e5b5ca3f69573548e226e50ef6..fb063e90b9a691bb632975280f140dfd7d6a70c1 100644
--- a/doc/user/application_security/dependency_scanning/dependency_scanning_sbom/_index.md
+++ b/doc/user/application_security/dependency_scanning/dependency_scanning_sbom/_index.md
@@ -19,7 +19,7 @@ title: Dependency scanning by using SBOM
 - [Enabled on GitLab.com, GitLab Self-Managed, and GitLab Dedicated](https://gitlab.com/gitlab-org/gitlab/-/issues/395692) in GitLab 17.5.
 - Released [lockfile-based Dependency Scanning](https://gitlab.com/gitlab-org/security-products/analyzers/dependency-scanning/-/blob/main/README.md?ref_type=heads#supported-files) analyzer as an [Experiment](../../../../policy/development_stages_support.md#experiment-features) in GitLab 17.4.
 - Released [Dependency Scanning CI/CD Component](https://gitlab.com/explore/catalog/components/dependency-scanning) version [`0.4.0`](https://gitlab.com/components/dependency-scanning/-/tags/0.4.0) in GitLab 17.5 with support for the [lockfile-based Dependency Scanning](https://gitlab.com/gitlab-org/security-products/analyzers/dependency-scanning/-/blob/main/README.md?ref_type=heads#supported-files) analyzer.
-- [Enabled by default with the latest Dependency Scanning CI/CD templates](https://gitlab.com/gitlab-org/gitlab/-/issues/519597) for Cargo, Conda, Cocoapods and Swift in GitLab 17.9.
+- [Enabled by default with the latest Dependency Scanning CI/CD templates](https://gitlab.com/gitlab-org/gitlab/-/issues/519597) for Cargo, Conda, Cocoapods, and Swift in GitLab 17.9.
 
 {{< /history >}}
 
@@ -383,7 +383,11 @@ lock file or dependency graph export detected.
 
 ### CycloneDX Software Bill of Materials
 
-> - Generally available in GitLab 15.7.
+{{< history >}}
+
+- Generally available in GitLab 15.7.
+
+{{< /history >}}
 
 The dependency scanning analyzer outputs a [CycloneDX](https://cyclonedx.org/) Software Bill of Materials (SBOM)
 for each supported lock or dependency graph export it detects. The CycloneDX SBOMs are created as job artifacts.
diff --git a/doc/user/application_security/vulnerability_report/_index.md b/doc/user/application_security/vulnerability_report/_index.md
index ceb0e8b46f6525707a744372c9f2f90c9597b7de..f1e641c052a382b8cc81ad3283378af94e5e601a 100644
--- a/doc/user/application_security/vulnerability_report/_index.md
+++ b/doc/user/application_security/vulnerability_report/_index.md
@@ -301,7 +301,11 @@ refreshed.
 
 ## Change or override vulnerability severity
 
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/16157) in GitLab 17.9 [with a flag](../../../administration/feature_flags.md) named `vulnerability_severity_override`. Disabled by default.
+{{< history >}}
+
+- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/16157) in GitLab 17.9 [with a flag](../../../administration/feature_flags.md) named `vulnerability_severity_override`. Disabled by default.
+
+{{< /history >}}
 
 {{< alert type="flag" >}}
 
diff --git a/doc/user/clusters/environments.md b/doc/user/clusters/environments.md
index 15c8f8bafd6c92e1b8b0c1ff3c28fa105eea5534..5297c1c9168d04fc15e54cfd8b900ab7f5cef024 100644
--- a/doc/user/clusters/environments.md
+++ b/doc/user/clusters/environments.md
@@ -12,7 +12,11 @@ title: Cluster Environments (deprecated)
 
 {{< /details >}}
 
-> - [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+{{< history >}}
+
+- [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+
+{{< /history >}}
 
 {{< alert type="warning" >}}
 
diff --git a/doc/user/clusters/management_project.md b/doc/user/clusters/management_project.md
index da855142252ce9a6c74707840cf5a0228e24f702..10038af444ce7dab84f046df147e3abe868a4713 100644
--- a/doc/user/clusters/management_project.md
+++ b/doc/user/clusters/management_project.md
@@ -12,7 +12,11 @@ title: Cluster management project (deprecated)
 
 {{< /details >}}
 
-> - [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+{{< history >}}
+
+- [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+
+{{< /history >}}
 
 {{< alert type="warning" >}}
 
diff --git a/doc/user/crm/_index.md b/doc/user/crm/_index.md
index d89b8a6cf8c7fac8e9eb30d41b37458726e7ad60..94e13afb8cf5bbc41e6b96eeca49c1541f2e2b2d 100644
--- a/doc/user/crm/_index.md
+++ b/doc/user/crm/_index.md
@@ -70,7 +70,11 @@ To enable customer relations management in a group or subgroup:
 
 ## Configure the contact source
 
-> - [Available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/167475) in GitLab 17.6.
+{{< history >}}
+
+- [Available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/167475) in GitLab 17.6.
+
+{{< /history >}}
 
 By default, contacts are sourced from an issue's top-level group.
 
diff --git a/doc/user/enterprise_user/_index.md b/doc/user/enterprise_user/_index.md
index 83c1329adad58b83d78a0a3470a8a8f9a4006466..5ae6f0684c972af65e0ad8226a1173125c51edb4 100644
--- a/doc/user/enterprise_user/_index.md
+++ b/doc/user/enterprise_user/_index.md
@@ -151,12 +151,14 @@ For GitLab instances with domain verification enabled, if the domain cannot be v
 
 {{< /alert >}}
 
-> **Notes:**
->
-> - Domain verification is **required for GitLab.com users** to be marked as enterprise users.
-> - [DNS propagation can take up to 24 hours](https://www.inmotionhosting.com/support/domain-names/dns-nameserver-changes/complete-guide-to-dns-records/), although it's usually a couple of minutes to complete. Until it completes, the domain shows as unverified.
-> - Once your domain has been verified, leave the verification record in place. Your domain is periodically reverified, and may be disabled if the record is removed.
-> - A valid certificate is not required for domain verification.
+{{< alert type="note" >}}
+
+- Domain verification is **required for GitLab.com users** to be marked as enterprise users.
+- [DNS propagation can take up to 24 hours](https://www.inmotionhosting.com/support/domain-names/dns-nameserver-changes/complete-guide-to-dns-records/), although it's usually a couple of minutes to complete. Until it completes, the domain shows as unverified.
+- Once your domain has been verified, leave the verification record in place. Your domain is periodically reverified, and may be disabled if the record is removed.
+- A valid certificate is not required for domain verification.
+
+{{< /alert >}}
 
 ### View domains in group
 
diff --git a/doc/user/markdown.md b/doc/user/markdown.md
index 054328b09497dba8b753677cc0fcbdc869d6c592..3016e6ad90eec7c8e84a4850b9c6f11c73f69a6f 100644
--- a/doc/user/markdown.md
+++ b/doc/user/markdown.md
@@ -1800,7 +1800,11 @@ $example = array(
 
 ## Includes
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/195798) in GitLab 17.7.
+{{< history >}}
+
+- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/195798) in GitLab 17.7.
+
+{{< /history >}}
 
 Use includes, or include directives, to add the content of a document inside another document.
 
diff --git a/doc/user/packages/debian_repository/_index.md b/doc/user/packages/debian_repository/_index.md
index 8670308540970d457795e3b3af66d10be8912293..3ca2b1b8b2a54a2ead3bdd6d03ac7ac168621d1d 100644
--- a/doc/user/packages/debian_repository/_index.md
+++ b/doc/user/packages/debian_repository/_index.md
@@ -13,7 +13,11 @@ title: Debian packages in the package registry
 
 {{< /details >}}
 
-> - [Deployed behind a feature flag](../../feature_flags.md), disabled by default.
+{{< history >}}
+
+- [Deployed behind a feature flag](../../feature_flags.md), disabled by default.
+
+{{< /history >}}
 
 {{< alert type="warning" >}}
 
diff --git a/doc/user/profile/personal_access_tokens.md b/doc/user/profile/personal_access_tokens.md
index 36901ca77995322b0094d6db2bc267c536d9f7ef..73d61c5a02284bc1ef74d3788869bfcd626f63e3 100644
--- a/doc/user/profile/personal_access_tokens.md
+++ b/doc/user/profile/personal_access_tokens.md
@@ -392,7 +392,11 @@ You can now create personal access tokens for a service account user with no exp
 
 {{< /details >}}
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/181053) in GitLab 17.10 [with a flag](../../administration/feature_flags.md) named `dpop_authentication`. Disabled by default.
+{{< history >}}
+
+- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/181053) in GitLab 17.10 [with a flag](../../administration/feature_flags.md) named `dpop_authentication`. Disabled by default.
+
+{{< /history >}}
 
 {{< alert type="flag" >}}
 
diff --git a/doc/user/project/clusters/gitlab_managed_clusters.md b/doc/user/project/clusters/gitlab_managed_clusters.md
index 943eb52cc158698b37cfbcf717f13d016a3f26af..b6b19472ba9aa02092398d18890a475cd8afcaaa 100644
--- a/doc/user/project/clusters/gitlab_managed_clusters.md
+++ b/doc/user/project/clusters/gitlab_managed_clusters.md
@@ -12,7 +12,11 @@ title: GitLab-managed clusters (deprecated)
 
 {{< /details >}}
 
-> - [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+{{< history >}}
+
+- [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+
+{{< /history >}}
 
 {{< alert type="warning" >}}
 
diff --git a/doc/user/project/deploy_boards.md b/doc/user/project/deploy_boards.md
index 1767f0c2240322a2ede511559750e231151d9365..96c9fee227c05817e8c954e151e6eebc04d1f6a6 100644
--- a/doc/user/project/deploy_boards.md
+++ b/doc/user/project/deploy_boards.md
@@ -12,7 +12,11 @@ title: Deploy boards (deprecated)
 
 {{< /details >}}
 
-> - [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+{{< history >}}
+
+- [Disabled on GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0.
+
+{{< /history >}}
 
 {{< alert type="warning" >}}
 
diff --git a/doc/user/project/issues/csv_import.md b/doc/user/project/issues/csv_import.md
index 9d507facbb378d6057898e3b8e437c202c4ba8de..706659dbb644c2a685e3897e34378d4bc0fce33b 100644
--- a/doc/user/project/issues/csv_import.md
+++ b/doc/user/project/issues/csv_import.md
@@ -12,7 +12,11 @@ title: Importing issues from CSV
 
 {{< /details >}}
 
-> - Additionally [allowed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/169256) for Planner role in GitLab 17.7.
+{{< history >}}
+
+- Additionally [allowed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/169256) for Planner role in GitLab 17.7.
+
+{{< /history >}}
 
 You can import issues to a project by uploading a CSV file with the following columns:
 
diff --git a/doc/user/project/merge_requests/stacked_diffs.md b/doc/user/project/merge_requests/stacked_diffs.md
index 4fb984e03e7f973b4ad7ceba704a8bd049a48daa..cf9e5d916b039508b9ed2c13d1bd7e1507778d11 100644
--- a/doc/user/project/merge_requests/stacked_diffs.md
+++ b/doc/user/project/merge_requests/stacked_diffs.md
@@ -14,7 +14,11 @@ title: Stacked diffs
 
 {{< /details >}}
 
-> - Released in [v1.42.0 of the GitLab CLI](https://gitlab.com/gitlab-org/cli/-/releases/v1.42.0) as an [experiment](../../../policy/development_stages_support.md#experiment).
+{{< history >}}
+
+- Released in [v1.42.0 of the GitLab CLI](https://gitlab.com/gitlab-org/cli/-/releases/v1.42.0) as an [experiment](../../../policy/development_stages_support.md#experiment).
+
+{{< /history >}}
 
 In the [GitLab CLI](https://gitlab.com/gitlab-org/cli), stacked diffs are a way of
 creating small changes that build upon each other to ultimately deliver a feature.
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
index f3efef78a91f9e5fd99710e605c8d020aed467c1..bc028e9fa6e415049d3f5d232c0296851a9260e6 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
@@ -62,12 +62,14 @@ Once you've met the requirements, enable Let's Encrypt integration:
 Once enabled, GitLab obtains a LE certificate and add it to the
 associated Pages domain. GitLab also renews it automatically.
 
-> **Notes:**
->
-> - Issuing the certificate and updating Pages configuration
->   **can take up to an hour**.
-> - If you already have an SSL certificate in domain settings it
->   continues to work until replaced by the Let's Encrypt certificate.
+{{< alert type="note" >}}
+
+Issuing the certificate and updating Pages configuration
+**can take up to an hour**.
+If you already have an SSL certificate in domain settings it
+continues to work until replaced by the Let's Encrypt certificate.
+
+{{< /alert >}}
 
 ## Troubleshooting