From e271183fe7176c86dc3266a4128051751366b8e6 Mon Sep 17 00:00:00 2001
From: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
Date: Thu, 23 Jun 2022 10:54:24 -0500
Subject: [PATCH] Added example for custom reader page

Signed-off-by: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
---
 docs/features/techdocs/addons.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/features/techdocs/addons.md b/docs/features/techdocs/addons.md
index a4e1de7d4f..fe1058b2ca 100644
--- a/docs/features/techdocs/addons.md
+++ b/docs/features/techdocs/addons.md
@@ -76,6 +76,18 @@ import { ReportIssue } from '@backstage/plugin-techdocs-module-addons-contrib';
 </Route>;
 ```
 
+If you are using a custom [TechDocs reader page](./how-to-guides.md#how-to-customize-the-techdocs-reader-page) your setup will be very similar, here's an example:
+
+```ts
+<Route path="/docs/:namespace/:kind/:name/*" element={<TechDocsReaderPage />}>
+  <TechDocsAddons>
+    <ReportIssue />
+    {/* Other addons can be added here. */}
+  </TechDocsAddons>
+  {techDocsPage} // This is your custom TechDocs reader page
+</Route>
+```
+
 The process for configuring Addons on the documentation tab on the entity page
 is very similar; instead of adding the `<TechDocsAddons>` registry under a
 `<Route>`, you'd add it as a child of `<EntityTechdocsContent />`: