guide-page-standard

Enablement guide page standard (The Forge)

Purpose: Define how Brainforge Enablement Guides render in The Forge without inventing a separate visual system from existing L&D lesson pages.

Audience: L&D authors and platform engineers implementing /learning/guides.

Related: guide-authoring-playbook.md · platform-page-standard.md · NORTH-STARS.md

Last updated: 2026-04-17

---

1. Core principles

1. Reuse the lesson-page pattern. Guides should feel like part of the same L&D product family as Quickstart and AI Accelerator.
2. Vault markdown stays the source of truth. Platform routes read from programs/guides/.
3. One guide = one page. No module redirects, no nested lesson routes in v1.
4. No progress tracking in v1. Guides are referenceable workflow aids, not completion-scored coursework.

---

2. Route shape

Surface	Path
Guide hub	/learning/guides
Guide detail	/learning/guides/{guideSlug}

The guide hub lists all active guides. Each guide detail page renders the guide README.md from the vault.

---

3. Guide hub page

The hub should include:

1. Breadcrumbs back to Learning & Development.
2. A short hero introducing Enablement Guides.
3. A card grid of available guides.
4. Optional intro markdown from programs/guides/README.md.

Each card should show:

• title
• short description
• audience
• estimated time
• a CTA to open the guide

---

4. Guide detail page

Use the same high-level anatomy as the current lesson pages:

1. breadcrumbs
2. lightweight back link to the guide hub
3. optional Zoom Clip embed if the guide markdown includes a Zoom Clip URL
4. markdown body rendered through the shared markdown component
5. sticky right sidebar on large screens

Sidebar content

Guide sidebars should be lighter than course sidebars. Include:

• guide details: audience, time, type, status
• related learning links
• other guide links

Do not include lesson progress, completion buttons, or module accordions.

---

5. Markdown behavior

Relative markdown links should resolve to:

• guide hub routes for programs/guides/README.md
• guide detail routes for programs/guides/{slug}/README.md
• GitHub blob links for other knowledge docs that do not have app routes

The markdown renderer should continue using the shared CertificationsMarkdown component so typography, tables, and links stay consistent with other L&D surfaces.

---

6. QA checklist

• /learning/guides loads without relying on client-only data.
• /learning/guides/{slug} renders the expected guide body from the vault.
• Mobile layout stacks content and sidebar cleanly.
• Guide links resolve correctly inside markdown.
• The first Zoom Clip URL is embedded and removed from the markdown body when present.
• Shared learning navigation includes Enablement Guides.
• No progress-tracking UI appears on guide pages.