diff --git a/_extensions/prerelease-docs-url/prerelease-docs-url.lua b/_extensions/prerelease-docs-url/prerelease-docs-url.lua
deleted file mode 100644
index 6e4fd947f2..0000000000
--- a/_extensions/prerelease-docs-url/prerelease-docs-url.lua
+++ /dev/null
@@ -1,62 +0,0 @@
--- Version-aware shortcode for linking to prerelease docs.
---
--- Usage: {{< prerelease-docs-url 1.9 >}}
---
--- Returns "prerelease." when the referenced version's docs live on
--- prerelease.quarto.org, or "" when they're on quarto.org.
-
-local function handler(args, kwargs, meta, raw_args, context)
-  local ref_version = quarto.shortcode.read_arg(args, 1)
-  if ref_version == nil then
-    return quarto.shortcode.error_output(
-      "prerelease-docs-url",
-      "requires a version argument, e.g. {{< prerelease-docs-url 1.9 >}}",
-      context
-    )
-  end
-  -- Strip surrounding quotes that may be preserved in text contexts
-  ref_version = ref_version:gsub('^"(.*)"$', '%1'):gsub("^'(.*)'$", '%1')
-
-  -- On the prerelease site, always link to prerelease
-  if quarto.project.profile:includes("prerelease-docs") then
-    return pandoc.Str("prerelease.")
-  end
-
-  -- Guard against missing or invalid version metadata
-  local version_str = meta["version"] and pandoc.utils.stringify(meta["version"]) or nil
-  if not version_str or version_str == "" then
-    return quarto.shortcode.error_output(
-      "prerelease-docs-url",
-      "missing 'version' in document metadata",
-      context
-    )
-  end
-
-  -- Compare referenced version to this branch's version using
-  -- pandoc.types.Version for correct element-wise comparison (1.12 > 1.9)
-  local ok_branch, branch_version = pcall(pandoc.types.Version, version_str)
-  local ok_ref, ref = pcall(pandoc.types.Version, ref_version)
-
-  if not ok_branch then
-    return quarto.shortcode.error_output(
-      "prerelease-docs-url",
-      "invalid metadata version '" .. version_str .. "'",
-      context
-    )
-  end
-  if not ok_ref then
-    return quarto.shortcode.error_output(
-      "prerelease-docs-url",
-      "invalid version argument '" .. ref_version .. "'",
-      context
-    )
-  end
-
-  if ref <= branch_version then
-    return pandoc.Str("")
-  else
-    return pandoc.Str("prerelease.")
-  end
-end
-
-return {["prerelease-docs-url"] = handler}
diff --git a/_extensions/prerelease/README.md b/_extensions/prerelease/README.md
new file mode 100644
index 0000000000..95cf8799f6
--- /dev/null
+++ b/_extensions/prerelease/README.md
@@ -0,0 +1,52 @@
+# Prerelease Extension
+
+Version-aware shortcodes for prerelease content on quarto-web. Both shortcodes use the `version` key from `_quarto.yml` (or `_quarto-prerelease-docs.yml` on the prerelease profile) to determine whether a feature version has been released.
+
+## Shortcodes
+
+### `prerelease-docs-url`
+
+Returns `"prerelease."` when the referenced version's docs live on prerelease.quarto.org, or `""` when they're on quarto.org. Use in link URLs:
+
+```markdown
+[documentation](https://{{< prerelease-docs-url 1.9 >}}quarto.org/docs/feature.html)
+```
+
+### `prerelease-callout`
+
+Shows a version-aware callout note. Two modes:
+
+**Feature docs** (default) — callout disappears after release:
+
+```markdown
+{{< prerelease-callout 1.9 >}}
+```
+
+- Unreleased: shows "Pre-release Feature" callout with link to prerelease download
+- Released: shows nothing
+
+**Blog posts** (`type="blog"`) — callout text changes after release:
+
+```markdown
+{{< prerelease-callout 1.9 type="blog" >}}
+```
+
+- Unreleased: shows "Pre-release Feature" callout with link to prerelease download
+- Released: shows "Quarto X.Y Feature" callout with link to stable download page
+
+## Version comparison logic
+
+On the **main site** (`version` = current stable release): a feature is unreleased when `ref_version > site_version`.
+
+On the **prerelease site** (profile `prerelease-docs`, `version` = current prerelease cycle): a feature is unreleased when `ref_version >= site_version`.
+
+The `>=` vs `>` difference handles the fact that the prerelease site's version equals the in-progress release, while main's version equals the last stable release.
+
+### Example scenarios (feature docs)
+
+| Phase | Site | `version` | ref | Unreleased? | Output |
+|---|---|---|---|---|---|
+| 1.9 in dev | main | 1.8 | 1.9 | 1.9 > 1.8 ✓ | Pre-release callout |
+| 1.9 in dev | prerelease | 1.9 | 1.9 | 1.9 >= 1.9 ✓ | Pre-release callout |
+| 1.9 released | main | 1.9 | 1.9 | 1.9 > 1.9 ✗ | Nothing |
+| 1.9 released | prerelease | 2.0 | 1.9 | 1.9 >= 2.0 ✗ | Nothing |
diff --git a/_extensions/prerelease-docs-url/_extension.yml b/_extensions/prerelease/_extension.yml
similarity index 50%
rename from _extensions/prerelease-docs-url/_extension.yml
rename to _extensions/prerelease/_extension.yml
index dabdf77cf6..628a0a7f50 100644
--- a/_extensions/prerelease-docs-url/_extension.yml
+++ b/_extensions/prerelease/_extension.yml
@@ -1,6 +1,6 @@
-title: Prerelease Docs URL
+title: Prerelease
 author: Quarto
 version: 0.0.1
 contributes:
   shortcodes:
-    - prerelease-docs-url.lua
+    - prerelease.lua
diff --git a/_extensions/prerelease/prerelease.lua b/_extensions/prerelease/prerelease.lua
new file mode 100644
index 0000000000..8022841811
--- /dev/null
+++ b/_extensions/prerelease/prerelease.lua
@@ -0,0 +1,152 @@
+-- Version-aware shortcodes for prerelease content.
+--
+-- prerelease-docs-url:
+--   {{< prerelease-docs-url 1.9 >}}
+--   Returns "prerelease." when the referenced version's docs live on
+--   prerelease.quarto.org, or "" when they're on quarto.org.
+--
+-- prerelease-callout:
+--   {{< prerelease-callout 1.9 >}}
+--   Shows a "Pre-release Feature" callout when the referenced version is
+--   unreleased. Shows nothing once the version is released.
+--
+--   {{< prerelease-callout 1.9 type="blog" >}}
+--   Blog mode: shows "Pre-release Feature" callout when unreleased,
+--   switches to "Quarto X.Y Feature" callout once released.
+--
+-- Both shortcodes use the `version` key from _quarto.yml metadata and
+-- the `prerelease-docs` profile to determine whether a version is released.
+
+--- Strip surrounding quotes from a shortcode argument.
+local function strip_quotes(s)
+  return s:gsub('^"(.*)"$', '%1'):gsub("^'(.*)'$", '%1')
+end
+
+--- Parse the version argument and site version metadata.
+-- Returns ref_version, branch_version (as pandoc.types.Version), or
+-- nil plus an error Blocks/Inlines on failure.
+local function parse_versions(shortcode_name, args, meta, context)
+  local ref_str = quarto.shortcode.read_arg(args, 1)
+  if ref_str == nil then
+    return nil, nil, quarto.shortcode.error_output(
+      shortcode_name,
+      "requires a version argument, e.g. {{< " .. shortcode_name .. " 1.9 >}}",
+      context
+    )
+  end
+  ref_str = strip_quotes(ref_str)
+
+  local version_str = meta["version"] and pandoc.utils.stringify(meta["version"]) or nil
+  if not version_str or version_str == "" then
+    return nil, nil, quarto.shortcode.error_output(
+      shortcode_name,
+      "missing 'version' in document metadata",
+      context
+    )
+  end
+
+  local ok_branch, branch_version = pcall(pandoc.types.Version, version_str)
+  if not ok_branch then
+    return nil, nil, quarto.shortcode.error_output(
+      shortcode_name,
+      "invalid metadata version '" .. version_str .. "'",
+      context
+    )
+  end
+
+  local ok_ref, ref_version = pcall(pandoc.types.Version, ref_str)
+  if not ok_ref then
+    return nil, nil, quarto.shortcode.error_output(
+      shortcode_name,
+      "invalid version argument '" .. ref_str .. "'",
+      context
+    )
+  end
+
+  return ref_version, branch_version, nil
+end
+
+--- Check whether a referenced version is unreleased.
+-- On prerelease site (profile prerelease-docs): ref >= site version
+-- On main site: ref > site version
+local function is_unreleased(ref_version, branch_version)
+  if quarto.project.profile:includes("prerelease-docs") then
+    return ref_version >= branch_version
+  else
+    return ref_version > branch_version
+  end
+end
+
+--- Parse a markdown string into pandoc Blocks.
+local function md_to_blocks(md)
+  return pandoc.read(md, "markdown").blocks
+end
+
+-- Shortcode: prerelease-docs-url
+local function docs_url_handler(args, kwargs, meta, raw_args, context)
+  local ref_version, branch_version, err = parse_versions(
+    "prerelease-docs-url", args, meta, context
+  )
+  if err then return err end
+
+  -- On the prerelease site, always link to prerelease
+  if quarto.project.profile:includes("prerelease-docs") then
+    return pandoc.Str("prerelease.")
+  end
+
+  if ref_version <= branch_version then
+    return pandoc.Str("")
+  else
+    return pandoc.Str("prerelease.")
+  end
+end
+
+-- Shortcode: prerelease-callout
+local function callout_handler(args, kwargs, meta, raw_args, context)
+  local ref_version, branch_version, err = parse_versions(
+    "prerelease-callout", args, meta, context
+  )
+  if err then return err end
+
+  local ref_str = strip_quotes(quarto.shortcode.read_arg(args, 1))
+  local callout_type = kwargs["type"] or ""
+  local is_blog = callout_type == "blog"
+  local unreleased = is_unreleased(ref_version, branch_version)
+
+  if unreleased then
+    -- Pre-release callout (both feature docs and blog)
+    local content = md_to_blocks(
+      "This feature is new in the upcoming Quarto " .. ref_str .. " release. " ..
+      "To use the feature now, you'll need to " ..
+      "[download and install](/docs/download/prerelease.qmd) " ..
+      "the Quarto pre-release."
+    )
+    return quarto.Callout({
+      type = "note",
+      title = "Pre-release Feature",
+      content = content,
+    })
+  end
+
+  if is_blog then
+    -- Released blog callout
+    local content = md_to_blocks(
+      "This post is part of a series highlighting new features in the " ..
+      ref_str .. " release of Quarto. Get the latest release on the " ..
+      "[download page](/docs/download/index.qmd)."
+    )
+    return quarto.Callout({
+      type = "note",
+      title = "Quarto " .. ref_str .. " Feature",
+      content = content,
+    })
+  end
+
+  -- Feature docs, already released: show nothing
+  return pandoc.Blocks({})
+end
+
+return {
+  ["prerelease-docs-url"] = docs_url_handler,
+  ["prerelease-callout"] = callout_handler,
+}
diff --git a/docs/advanced/jupyter/kernel-execution.qmd b/docs/advanced/jupyter/kernel-execution.qmd
index 9f261f318d..c9ebb994b0 100644
--- a/docs/advanced/jupyter/kernel-execution.qmd
+++ b/docs/advanced/jupyter/kernel-execution.qmd
@@ -25,7 +25,7 @@ In `python` and `julia` kernels, the setup and cleanup cells are defined by the
 
 ### Adding support to a Jupyter kernel
 
-{{< include /docs/prerelease/1.5/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.5 >}}
 
 If a Jupyter kernel wants to execute in awareness of Quarto's context, it should signal its support by adding the following files to the kernelspec directory:
 
@@ -42,7 +42,7 @@ See the [source for more](https://github.com/quarto-dev/quarto_echo_kernel).
 
 ## Quarto document options
 
-{{< include /docs/prerelease/1.5/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.5 >}}
 
 Jupyter kernels can have access to a number of Quarto options that can affect cell execution.
 
@@ -74,7 +74,7 @@ Quarto offers built-in support for `julia` and `python` kernels by default, see
 
 ### Adding support to a Jupyter kernel
 
-{{< include /docs/prerelease/1.5/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.5 >}}
 
 Arbitrary Jupyter kernels can indicate support for daemons. To do so, provide a `quarto_setup_cell` file in the kernelspec directory so that setup cells can be executed, and ensure that the execution of the setup cell returns an output result with metadata indicating support for running as a daemon. The supported metadata options are:
 
diff --git a/docs/authoring/brand.qmd b/docs/authoring/brand.qmd
index 5af90da4f9..578cbbc4ed 100644
--- a/docs/authoring/brand.qmd
+++ b/docs/authoring/brand.qmd
@@ -780,7 +780,7 @@ In most cases, these assets should be committed to source control.
 
 ### `quarto use brand`
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 The `quarto use brand` command copies brand files from an external source into your project's `_brand/` directory. To use it, navigate to your project directory and run:
 
diff --git a/docs/authoring/diagrams.qmd b/docs/authoring/diagrams.qmd
index 7ef0dc2b16..4c50090e49 100644
--- a/docs/authoring/diagrams.qmd
+++ b/docs/authoring/diagrams.qmd
@@ -234,7 +234,7 @@ To include code for `{dot}`, add `//| echo: true` to the top of the cell. For ex
 
 ## Chrome Install {#chrome-install}
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 For printing to output formats like `pdf` or `docx`, diagram rendering makes use of the Chrome or Edge web browser to create a high-quality PNG.
 
diff --git a/docs/blog/posts/2023-03-13-code-annotation/index.qmd b/docs/blog/posts/2023-03-13-code-annotation/index.qmd
index 21fb694c9b..8488de3121 100644
--- a/docs/blog/posts/2023-03-13-code-annotation/index.qmd
+++ b/docs/blog/posts/2023-03-13-code-annotation/index.qmd
@@ -14,7 +14,7 @@ image-alt: "Screenshot a code chunk with annotations. Annotations appear in the
 code-annotations: below
 ---
 
-{{< include ../_quarto-1.3-feature.qmd >}}
+{{< prerelease-callout 1.3 type="blog" >}}
 
 Code blocks and executable code cells in Quarto may now include line-based annotations. Line-based annotations provide a way to attach explanation to lines of code much like footnotes.
 
diff --git a/docs/blog/posts/2023-03-15-multi-format/index.qmd b/docs/blog/posts/2023-03-15-multi-format/index.qmd
index 89bc6781f1..7d065fd9cd 100644
--- a/docs/blog/posts/2023-03-15-multi-format/index.qmd
+++ b/docs/blog/posts/2023-03-15-multi-format/index.qmd
@@ -17,7 +17,7 @@ format:
   docx: default
 ---
 
-{{< include ../_quarto-1.3-feature.qmd >}}
+{{< prerelease-callout 1.3 type="blog" >}}
 
 Starting in Quarto 1.3, HTML pages (either standalone or in a website) can automatically include links to other formats specified in the document front matter. For example, the following document front matter:
 
diff --git a/docs/blog/posts/2023-03-17-jupyter-cell-embedding/index.qmd b/docs/blog/posts/2023-03-17-jupyter-cell-embedding/index.qmd
index 22f07a3e95..368d19b667 100644
--- a/docs/blog/posts/2023-03-17-jupyter-cell-embedding/index.qmd
+++ b/docs/blog/posts/2023-03-17-jupyter-cell-embedding/index.qmd
@@ -13,7 +13,7 @@ image: embed.png
 image-alt: "A screenshot of a Quarto page that includes a plot, below the plot is the phrase Source: penguins.ipynb."
 ---
 
-{{< include ../_quarto-1.3-feature.qmd >}}
+{{< prerelease-callout 1.3 type="blog" >}}
 
 Starting in Quarto 1.3, you can include the output of an external Jupyter notebook in a Quarto document with the `embed` shortcode. To embed a notebook cell, provide the path to a Jupyter Notebook and a cell identifier. For example, this notebook called `penguins.ipynb` has a cell labelled `fig-bill-scatter`:
 
diff --git a/docs/blog/posts/2023-03-20-confluence/index.qmd b/docs/blog/posts/2023-03-20-confluence/index.qmd
index e27a836459..417fbabd3b 100644
--- a/docs/blog/posts/2023-03-20-confluence/index.qmd
+++ b/docs/blog/posts/2023-03-20-confluence/index.qmd
@@ -13,7 +13,7 @@ image: confluence-logo-gradient-blue-attribution_rgb@2x.png
 image-alt: "Atlassian Confluence Logo"
 ---
 
-{{< include ../_quarto-1.3-feature.qmd >}}
+{{< prerelease-callout 1.3 type="blog" >}}
 
 [Atlassian Confluence](https://www.atlassian.com/software/confluence) is a publishing platform for supporting team collaboration. Confluence has a variety of hosting options which include both free and paid subscription plans.
 
diff --git a/docs/blog/posts/2026-03-05-pdf-accessibility-and-standards/index.qmd b/docs/blog/posts/2026-03-05-pdf-accessibility-and-standards/index.qmd
index 3de0ba61b8..627fec2cb2 100644
--- a/docs/blog/posts/2026-03-05-pdf-accessibility-and-standards/index.qmd
+++ b/docs/blog/posts/2026-03-05-pdf-accessibility-and-standards/index.qmd
@@ -8,7 +8,7 @@ image: thumbnail.png
 image-alt: "Quarto icon, PDF file icon, accessibility icon, and validation shield"
 ---
 
-{{< include ../_quarto-1.9-feature.qmd >}}
+{{< prerelease-callout 1.9 type="blog" >}}
 
 2025 was a big year for PDF accessibility. LaTeX and Typst both released support for PDF tagging and accessibility standards, just in time for new regulations in the [EU](https://en.wikipedia.org/wiki/European_Accessibility_Act) (June 2025) and [US](https://accessible.org/ada-title-ii-web-accessibility/) (April 2026).  
 
diff --git a/docs/blog/posts/_quarto-1.3-feature.qmd b/docs/blog/posts/_quarto-1.3-feature.qmd
deleted file mode 100644
index 2fa830a619..0000000000
--- a/docs/blog/posts/_quarto-1.3-feature.qmd
+++ /dev/null
@@ -1,5 +0,0 @@
-::: callout-note
-## Quarto 1.3 Feature
-
-This post is part of a series highlighting new features in the 1.3 release of Quarto. Get the latest release the [download page](/docs/download/index.qmd)
-:::
diff --git a/docs/blog/posts/_quarto-1.9-feature.qmd b/docs/blog/posts/_quarto-1.9-feature.qmd
deleted file mode 100644
index 70e674e8fb..0000000000
--- a/docs/blog/posts/_quarto-1.9-feature.qmd
+++ /dev/null
@@ -1,5 +0,0 @@
-::: callout-note
-## Pre-release Feature
-
-This feature is new in the upcoming Quarto 1.9 release. To use the feature now, you'll need to [download and install](/docs/download/prerelease.qmd) the Quarto pre-release.
-:::
diff --git a/docs/books/book-output.qmd b/docs/books/book-output.qmd
index b086fe6f03..cfc62b67d4 100644
--- a/docs/books/book-output.qmd
+++ b/docs/books/book-output.qmd
@@ -159,7 +159,7 @@ At this point you should probably make a copy or git branch of the `_book` direc
 
 ## Typst Output
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 Quarto books can be rendered to PDF using [Typst](https://typst.app). When you specify `format: typst` for a book project, Quarto automatically uses the bundled [orange-book](https://typst.app/universe/package/orange-book) format extension, which provides textbook styling.
 
diff --git a/docs/computations/julia.qmd b/docs/computations/julia.qmd
index 1ce13b247f..0376d3afd9 100644
--- a/docs/computations/julia.qmd
+++ b/docs/computations/julia.qmd
@@ -108,7 +108,7 @@ display(plot(x -> sin(4x), y -> sin(5y), 0, 2))
 
 # Using the `julia` engine
 
-{{< include /docs/prerelease/1.5/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.5 >}}
 
 ## Installation {#installation-julia-engine}
 
diff --git a/docs/extensions/engine.qmd b/docs/extensions/engine.qmd
index 12a59a1942..44afd4fc85 100644
--- a/docs/extensions/engine.qmd
+++ b/docs/extensions/engine.qmd
@@ -2,7 +2,7 @@
 title: "Engine Extensions"
 ---
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 Engine extensions are Quarto extensions that provide an execution engine for running code blocks and capturing their output in Quarto documents.
 
diff --git a/docs/output-formats/_document-options-syntax-highlighting.md b/docs/output-formats/_document-options-syntax-highlighting.md
index 745457697e..85414b5668 100644
--- a/docs/output-formats/_document-options-syntax-highlighting.md
+++ b/docs/output-formats/_document-options-syntax-highlighting.md
@@ -2,7 +2,7 @@
 
 ::: {.content-visible when-meta="doc-type.typst"}
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 :::
 
diff --git a/docs/output-formats/typst-custom.qmd b/docs/output-formats/typst-custom.qmd
index 3cf324a1a6..6a2427c394 100644
--- a/docs/output-formats/typst-custom.qmd
+++ b/docs/output-formats/typst-custom.qmd
@@ -54,7 +54,7 @@ Additional resources you might find useful when creating custom formats include:
 
 ## Book Format Extensions
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 A Typst book format extension includes template partials that configure the underlying Typst package, and a Lua filter that transforms Quarto's book structure into package-specific commands. The core partials are:
 
diff --git a/docs/output-formats/typst.qmd b/docs/output-formats/typst.qmd
index 8a78f15fdf..a3e1f088fe 100644
--- a/docs/output-formats/typst.qmd
+++ b/docs/output-formats/typst.qmd
@@ -219,7 +219,7 @@ This gets compiled to
 
 ## Theorems
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 Quarto uses the [theorion](https://typst.app/universe/package/theorion) package for theorems in Typst output. You can control the appearance of theorems, lemmas, proofs, and related blocks using the `theorem-appearance` option:
 
diff --git a/docs/prerelease/1.3/_pre-release-feature.qmd b/docs/prerelease/1.3/_pre-release-feature.qmd
deleted file mode 100644
index 233ea1a591..0000000000
--- a/docs/prerelease/1.3/_pre-release-feature.qmd
+++ /dev/null
@@ -1,5 +0,0 @@
-::: {.callout-note}
-## Pre-release Feature
-
-This feature is new in the upcoming Quarto 1.3 release. To use the feature now, you'll need to [download](/docs/download/prerelease.qmd) and install the Quarto pre-release.
-:::
diff --git a/docs/prerelease/1.4/_pre-release-feature.qmd b/docs/prerelease/1.4/_pre-release-feature.qmd
deleted file mode 100644
index 49c157a8c1..0000000000
--- a/docs/prerelease/1.4/_pre-release-feature.qmd
+++ /dev/null
@@ -1,5 +0,0 @@
-::: {.callout-note}
-## Pre-release Feature
-
-This feature is new in the upcoming Quarto 1.4 release. To use the feature now, you'll need to [download](/docs/download/prerelease.qmd) and install the Quarto pre-release.
-:::
diff --git a/docs/prerelease/1.5/_pre-release-feature.qmd b/docs/prerelease/1.5/_pre-release-feature.qmd
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/prerelease/1.6/_pre-release-feature.qmd b/docs/prerelease/1.6/_pre-release-feature.qmd
deleted file mode 100644
index 77d0704919..0000000000
--- a/docs/prerelease/1.6/_pre-release-feature.qmd
+++ /dev/null
@@ -1,5 +0,0 @@
-::: {.callout-note}
-## Pre-release Feature
-
-This feature is new in the upcoming Quarto 1.6 release. To use the feature now, you'll need to [download](/docs/download/prerelease.qmd) and install the Quarto pre-release.
-:::
diff --git a/docs/prerelease/1.7/_pre-release-feature.qmd b/docs/prerelease/1.7/_pre-release-feature.qmd
deleted file mode 100644
index ab049226f0..0000000000
--- a/docs/prerelease/1.7/_pre-release-feature.qmd
+++ /dev/null
@@ -1,5 +0,0 @@
-::: {.callout-note}
-## Pre-release Feature
-
-This feature is new in the upcoming Quarto 1.7 release. To use the feature now, you'll need to [download](/docs/download/prerelease.qmd) and install the Quarto pre-release.
-:::
diff --git a/docs/prerelease/1.8/_pre-release-feature.qmd b/docs/prerelease/1.8/_pre-release-feature.qmd
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/prerelease/1.9/_pre-release-feature.qmd b/docs/prerelease/1.9/_pre-release-feature.qmd
deleted file mode 100644
index eb8562bc38..0000000000
--- a/docs/prerelease/1.9/_pre-release-feature.qmd
+++ /dev/null
@@ -1,5 +0,0 @@
-::: {.callout-note}
-## Pre-release Feature
-
-This feature is new in the upcoming Quarto 1.9 release. To use the feature now, you'll need to [download](/docs/download/prerelease.qmd) and install the Quarto pre-release.
-:::
diff --git a/docs/publishing/hugging-face.qmd b/docs/publishing/hugging-face.qmd
index 8f91fbf58d..8bdffd2e0c 100644
--- a/docs/publishing/hugging-face.qmd
+++ b/docs/publishing/hugging-face.qmd
@@ -80,7 +80,7 @@ You can edit these files directly in the Hugging Face UI but we reccommend cloni
 
 ## Publish Command
 
-{{< include ../prerelease/1.5/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.5 >}}
 
 The `quarto publish huggingface` command facilitates a workflow where you [make and preview edits](#edit-and-preview) locally before [publishing](#publish) to your Hugging Face space. Before using the command you'll need to complete some [Setup](#setup).
 
diff --git a/docs/publishing/posit-connect-cloud.qmd b/docs/publishing/posit-connect-cloud.qmd
index 9d23f51126..9a45ac8808 100644
--- a/docs/publishing/posit-connect-cloud.qmd
+++ b/docs/publishing/posit-connect-cloud.qmd
@@ -14,7 +14,7 @@ provider:
         default web browser, then press Enter or 'Y' to authorize.
 ---
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 ## Overview
 
diff --git a/docs/websites/website-search.qmd b/docs/websites/website-search.qmd
index 0293e7fcb3..9abb9a1a15 100644
--- a/docs/websites/website-search.qmd
+++ b/docs/websites/website-search.qmd
@@ -83,7 +83,7 @@ When you click a search result, Quarto navigates to the destination page and hig
 
 The highlighting is driven by a `?q=` URL parameter. You can manually add `?q=term` to any page URL to highlight occurrences of that term — useful for sharing links that draw attention to specific content.
 
-{{< include /docs/prerelease/1.9/_pre-release-feature.qmd >}}
+{{< prerelease-callout 1.9 >}}
 
 Highlights remain visible until you navigate away from the page. When a match is found inside a [tabset](/docs/output-formats/html-basics.qmd#tabsets), the correct tab is automatically activated to reveal the highlighted content, including nested and grouped tabsets. Multi-word search terms are highlighted correctly even when they span across formatting boundaries such as bold, italic, code spans, or syntax-highlighted code blocks.