diff --git a/content/pages/atr.md b/content/pages/atr.md
new file mode 100644
index 000000000..d8dd224e5
--- /dev/null
+++ b/content/pages/atr.md
@@ -0,0 +1,13 @@
+Title: Apache Trusted Releases
+license: https://www.apache.org/licenses/LICENSE-2.0
+
+# Apache Trusted Releases
+
+The Apache Trusted Releases (ATR) platform performs two key functions:
+
+  - it simplifies the process of preparing and approving a PMC's release of code
+  - it strengthens security around the release process so that both the project releasing the code and the users downloading it can be confident that the package contains only what it should
+
+In August 2026, ATR is moving into **beta testing**. Its documentation during this period is available at <a href="https://release-test.apache.org/docs/introduction-to-atr" target="_blank">release-test.apache.org/docs/introduction-to-atr</a>.
+
+When ATR is in general availability, its documentation will be at <a href="https://releases.apache.org/docs/introduction-to-atr" target="_blank">releases.apache.org/docs/introduction-to-atr</a>.
diff --git a/content/pages/release-download-pages.md b/content/pages/release-download-pages.md
index 25de72304..c42a6856a 100644
--- a/content/pages/release-download-pages.md
+++ b/content/pages/release-download-pages.md
@@ -3,12 +3,14 @@ license: https://www.apache.org/licenses/LICENSE-2.0
 
 Your project's release download page is where people can download your product's latest release(s). This page describes how a release manager can put such a page together.
 
+**Note**: Projects using the **Apache Trusted Releases (ATR)** platform should consult its [documentation](atr.html), which in part supersedes this information.
+
 Review
 
   - the policy on [release distribution](release-distribution.html) if you are unsure of the best way to use the project download page
   - guidelines on [signing releases](release-signing.html)
 
-## Contents ##
+## Contents 
 
 <ul>
 <li><a href="#links">Download links</a></li>
@@ -42,7 +44,7 @@ Your Apache project's download page:
 
 <h3 id="current-and-older-releases">Current and older releases<a class="headerlink" href="#current-and-older-releases" title="Permanent link">&para;</a></h3>
 
-Do **not** keep software distributions on your project's website. Move them to one of the two software distribution sites:
+Do **not** keep software distributions on your project's website. Move them to one of these two sites:
 
   - **Current public releases** appear on `downloads.apache.org/`. Place current, official releases that the PMC has approved for end-users on the main public release site. Make all changes at <a href="https://dist.apache.org/repos/dist/release/" target="_blank">`https://dist.apache.org/repos/dist/release/`</a>.
 
diff --git a/content/pages/release-integrity-primer.md b/content/pages/release-integrity-primer.md
index 33ef93434..c39100677 100644
--- a/content/pages/release-integrity-primer.md
+++ b/content/pages/release-integrity-primer.md
@@ -1,6 +1,9 @@
 title: Handling Release Artifact Integrity Errors at the ASF
 license: https://www.apache.org/licenses/LICENSE-2.0
 
+## Release Integrity Primer
+
+**Note**: Projects using the **Apache Trusted Releases (ATR)** platform should consult its [documentation](atr.html), which in part supersedes this information.
 
 This page will help you resolve [release distribution policy](https://infra.apache.org/release-distribution) errors that our [Download Integrity Checker](https://github.com/apache/infrastructure-download-integrity-checker) discovers.
 Each reported error has an accompanying error code (`CHKxx`). The code will help you resolve issues by using the matrix below:
diff --git a/content/pages/release-publishing.md b/content/pages/release-publishing.md
index 35b37c37a..90305de45 100644
--- a/content/pages/release-publishing.md
+++ b/content/pages/release-publishing.md
@@ -1,10 +1,12 @@
 Title: Release Creation Process
 license: https://www.apache.org/licenses/LICENSE-2.0
 
-These best practices help guide a PMC through the steps to create and publish an Apache software product release. It complements the formal <a href="https://www.apache.org/legal/release-policy.html" target="_blank">Apache Release Policy</a>, defining what must be in a software release, and [Release Distribution Policy](release-distribution.html).
+These best practices help guide a PMC through the steps to create and publish an Apache software product release. They complement the formal <a href="https://www.apache.org/legal/release-policy.html" target="_blank">Apache Release Policy</a>, defining what must be in a software release, and [Release Distribution Policy](release-distribution.html).
 
 Every Apache Software Foundation project software release must meet requirements for content, process, and publication. These requirements ensure that Apache contributors and users benefit from appropriate legal protection the ASF provides, and reflect the Foundation's goals of open, collaborative software development.
 
+**Note**: Projects using the **Apache Trusted Releases (ATR)** platform should consult its [documentation](atr.html), which in part supersedes this information.
+
 ## Contents ##
 
   - <a href="#definition">An Apache release</a>
@@ -41,7 +43,9 @@ By default, only PMC members can publish release artifacts to https://dist.apach
 
 Allowing Committers to publish release artifacts requires project consensus, so include a link to an email thread with that consensus.
 
-***Release managers do the mechanical work; but the PMC in general, and the PMC chair in particular (as an officer of the Foundation), remains responsible for compliance with ASF requirements.***
+**Note**: Any PMC member of a project using the **ATR** platform can assign a **specific Committer** to the role of release manager, rather than giving blanket permission to all Committers of the PMC. To do this, open a Jira ticket for ATR with the details of your request.
+
+***Release managers do the mechanical work; but the PMC in general, and the PMC chair in particular (as an officer of the Foundation), remain responsible for compliance with ASF requirements.***
 
 <h2 id="valid">A valid release package<a class="headerlink" href="#valid" title="Permanent link">&para;</a></h2>
 
@@ -134,3 +138,5 @@ As a rule of thumb, projects should currently:
 <h2 id="faqs">FAQs<a class="headerlink" href="#faqs" title="Permanent link">&para;</a></h2>
 
   - **How do I archive an old release?** `downloads.apache.org` is automatically archived every four hours. Therefore, a copy of every official release exists in the archives. Just delete the copy of the release that is in your project's dist directory. Remember to update any links from the download page related to that release.
+
+**Note**: if your project is using the [Apache Trusted Releases](atr.html) (ATR) platform, there is no delay in archiving older releases.