ui: remove homepage documentation button

docs/contribution/diagrams.md

@@ -37,10 +37,10 @@ import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
 <ArchifyDiagram name="organization-structure" title="Illustrative organization structure" />
 ```
 
-Supply a text alternative below each diagram. The wrapper uses a local, base-path-aware iframe with a descriptive title, scripts and downloads enabled, and no same-origin or parent-navigation permissions. A full-viewer link provides a wider canvas. Generated output is ignored by Git and rebuilt in CI.
+Supply a text alternative below each diagram. The wrapper uses a local, base-path-aware iframe with a descriptive title, scripts and downloads enabled, and no same-origin or parent-navigation permissions. A full-viewer link provides a wider canvas in a new tab; that direct page is not iframe-sandboxed. Only publish reviewed, trusted diagrams, and do not describe iframe isolation as protection for the standalone route. Generated output is ignored by Git and rebuilt in CI.
 
 ## Integration boundaries
 
-The portal remains Docusaurus/React/TypeScript with pnpm. It uses the actual upstream renderer, not a look-alike diagram implementation. No Astro site, global agent installation, hosted rendering service, or AI API was added. The integration disables Archify update networking and does not run its installation commands.
+The portal remains Docusaurus/React/TypeScript with pnpm. It uses the actual upstream renderer, not a look-alike diagram implementation. No Astro site, global agent installation, hosted rendering service, or AI API was added. The integration disables Archify update networking and does not run its installation commands. This does not disable every possible build-time request: upstream can fetch authored, digest-pinned brand URLs. The current example contains none. Review external asset sources deliberately; update-check suppression is not an offline guarantee.
 
 Upgrades are deliberate: review the upstream diff and licenses, update the provenance record and vendor checksums, then run tests, diagram validation, production build, and browser checks. Do not edit upstream files for portal styling.

docs/core/maintain.md

@@ -19,7 +19,16 @@ Open the development server address printed in the terminal. The site uses the `
 
 ## Add or change a page
 
-Edit Markdown in `docs/`. Include `title` and `description` frontmatter and add the page ID to `sidebars.ts`. Keep the documentation’s future scope open until it is agreed.
+Include `title` and `description` frontmatter. Place each page in its owning section and add its document ID to that section’s sidebar:
+
+| Section | Content directory | Sidebar configuration |
+| --- | --- | --- |
+| Organization | `docs/organization/` | `sidebars/organization.ts` |
+| Strategy | `docs/strategy/` | `sidebars/strategy.ts` |
+| Contribution | `docs/contribution/` | `sidebars/contribution.ts` |
+| Portal maintenance and reference | `docs/core/` | `sidebars.ts` |
+
+Keep these content roots disjoint. Preserve existing URLs when moving pages. Specific AI initiatives and organizational reporting lines remain subject to agreement.
 
 ## Validate the change
 

src/pages/index.tsx

@@ -11,7 +11,6 @@ export default function Home(): React.ReactElement {
             <p className="eyebrow">ELDORADO / AI STRATEGY</p>
             <h1>Eldorado<br/><span>Powered By AI</span></h1>
             <p className="hero-description">Strategy and direction for an AI-powered Eldorado.</p>
-            <Link className="button button--primary button--lg" to="/docs/overview/">Explore the documentation <span aria-hidden="true">→</span></Link>
             <p className="hero-note">A starting point for shaping the strategy.</p>
           </div>
           <div className="hero-art" aria-hidden="true">