Pride Wiki Viewer — Wiki Entry Point

Purpose: Read-only static HTML knowledge base (Quartz) that renders the Pride wiki as a professional, browsable website. Primary user is Mat O’Keefe (CEO, non-technical), who uses it to browse and search business intelligence and queries the wiki through Claude Cowork.

Loaded by: _wiki-viewer-project-setup/INSTRUCTIONS.md (Cowork) and pride-wiki/CLAUDE.md (which is a query guide for Mat’s Claude, not a build-rules file).

Always load at session start

• Mat Wiki Access Implementation — The architecture decision: Quartz v4 + Cloudflare Pages + Cloudflare Access, 3-phase implementation (Session 12 approval)
• Perplexity Quartz Evaluation — Capabilities, setup, 10 known issues, CEO customisation (5 dimensions, 2–3 dev-days), 10 live deployments evaluated
• Perplexity Knowledge Base UX Research — Navigation, landing page, search UX, mobile design, accessibility for non-technical CEO; 10 exemplar sites
• Perplexity SSG Stack Evaluation — 8 SSGs, 7 search engines, hosting, access control compared

Load when work touches…

Viewer UX and design

• Humphrey Design System — Visual consistency if we want the viewer to feel connected to Humphrey
• Brand Positioning — Brand voice/identity the viewer should reflect
• Humphrey UI Overhaul Research — Dashboard patterns that may inform the viewer’s landing page

Content rendering

• Mat O’Keefe — Primary user; non-technical; majority shareholder; context for UX decisions
• Single-Point-of-Failure Leadership — Why Mat needs this kind of access in the first place

Access control / privacy

• Shared Account Security — 2FA concentration risk; informs auth decisions for the viewer
• Shareholder Registry and Email Analysis — Sensitive content that must NEVER appear in the public wiki viewer

Sync infrastructure

• pride-turnaround/_wiki/ → pride-wiki/content/ sync script (currently in pride-wiki/scripts/) — flagged as needing attention, 10-day drift observed 2026-04-24

Active decisions

• Mat Wiki Access Implementation — Quartz v4 + Cloudflare Pages + Cloudflare Access ($0/month); approved Session 12

Source documents

• Perplexity SSG Stack Evaluation — SSG comparison
• Perplexity Knowledge Base UX Research — Non-technical-CEO UX patterns
• Perplexity Quartz Evaluation — Deep dive on Quartz specifically

Analysis relevant to this project

• None filed yet — most implementation detail lives in pride-wiki/_specs/WIKI-VIEWER-BUILD.md

Cross-project context

• The wiki itself — Wiki Viewer renders content from pride-turnaround/_wiki/. Any content change in the source wiki flows into the viewer on sync. Treat the source wiki as read-through, not edit-in-place.
• ops — Ops decides what content is sensitive and whether it belongs in the wiki at all.
• finance — Financial data in the wiki is rendered publicly (within the viewer’s access control). Ensure figures in the wiki are appropriate for the viewer’s audience.
• humphrey — If Humphrey wants to cross-link to wiki pages (e.g., “see context for this alert”), the Wiki Viewer is the URL target.

Critical constraints

• Read-only from the viewer’s side. Mat and anyone else with Cloudflare Access can view, not edit. Edits happen in Obsidian against the source vault (pride-turnaround/_wiki/).
• No sensitive data in the viewer. Shareholder registry, individual financial figures, and personal contact details must not sync into pride-wiki/content/ unless explicitly gated. Current state: the sync script is permissive — audit before each sync.
• Cowork writes no code here. Per _wiki-viewer-project-setup/INSTRUCTIONS.md, all code changes to the Quartz site go through Claude Code via specs in pride-wiki/_specs/.

Open issues (as of 2026-04-24)

• pride-wiki/content/ is 10 days stale vs pride-turnaround/_wiki/ — needs sync run
• pride-wiki/CLAUDE.md references stale page counts (“188+ pages”, “entities (19 pages)”) — corrected in WIKI-META-1

Recent updates

• 2026-04-24 — Sub-index created (WIKI-META-1)