Pride Website — Wiki Entry Point

Purpose: Complete rebuild of the public-facing website for Pride of Our Footscray. Replaces the existing Google Sites presence with a modern, investor-ready experience primarily serving patrons and the community, and supporting a capital raise.

Loaded by: _website-project-setup/INSTRUCTIONS.md (Cowork) and pride-website/CLAUDE.md (Claude Code).

Always load at session start

These are the pages Cowork needs to have context for before making copy, content-strategy, or regulatory decisions on the website.

• Pride of Our Footscray — Venue identity, address, operating status, brand narrative
• Brand Positioning — Brand identity and market positioning that the site must reflect
• Community Ownership Narrative — Brand vs reality tension: the “community-owned” framing vs the Pty Ltd structure — critical for Investor section copy honesty
• Capital Raise Strategy — Why the website exists in its investor-ready form; shapes the /invest/* section entirely
• Capital Raise Blockers — The five structural barriers; affects what can be claimed publicly vs what’s gated

Load when work touches…

Regulatory / investor copy

• Corporate Structure Breach — s 113 breach; affects what capital-raise claims are defensible
• Co-operative Conversion Pathway — Current governance reform path; feeds the “what we’re doing about it” investor narrative
• Corporate Structure Reform — Decision on distributing co-operative conversion
• Shareholder Engagement — Context for the Register Interest form and shareholder-facing copy
• Shareholder Structure and Rights — Ownership facts (used generically, never with individual data)
• Pty Ltd Share Issue Compliance Research — The authoritative source on what can and cannot be published re: shares

Events / programming pages

• Programming Model — Structure of event types, revenue mix, frequency
• Programming Calendar — Current weekly rotation
• Drag Bingo, Themed Nights, DJ and Club Nights, Live Music, Cabaret and Burlesque, Pride Comedy, Speed Dating Events, Trivia Nights — Category anchors for event detail pages
• Event Pricing Benchmarks — If any pricing language appears on the site

Venue / function pages

• Venue Operations — Opening hours, capacity, spaces
• Function Booking Process — Gap analysis; informs what the function enquiry flow should collect
• Kitchen Expansion — Forward-looking content (do not claim kitchen is open until it is)
• Food Menu Strategy — Menu copy source

Merch / commerce

• Square POS — Commerce platform that the headless merch integration reads from

Accessibility

• Disability Access and Inclusion — Obligations and current staged implementation; informs /find-us accessibility copy

Marketing / audience

• Audience Development, Customer Segmentation and Engagement, Social Media Presence, Content Calendar — Context for tone, voice, and channel alignment

Active decisions

• Kitchen Opening Decision — Approved; kitchen content can be drafted but not yet “open”
• Theatre Restaurant Model — Saturday programming pivot confirmed 11 Apr 2026; affects events page
• Corporate Structure Reform — Recommended conversion to distributing co-operative; pending Mat + legal sign-off; directly affects investor copy
• Mat Wiki Access Implementation — Parallel project; informs cross-linking between public site and wiki viewer

Source documents

• Pride Venue Benchmarks Research — Revenue density, labour, COGS benchmarks; feeds investor “case” copy
• Melbourne LGBTQ Entertainment Landscape Research — Competitive positioning for About and Invest narrative
• Grants Report April 2026 — Supporting evidence for community-impact story
• Accessibility Obligations Research — Authoritative source for accessibility claims on the site
• Perplexity Knowledge Base UX Research — UX exemplars; informs the Wiki-Viewer-style investor data room pattern
• Mat Meeting 11 April 2026 — Source for Theatre Restaurant pivot language

Analysis relevant to this project

• WEB-META-1 CLAUDE.md Level-Up — Rules baked into pride-website/CLAUDE.md
• WEB-AG-5 QA Findings — QA baseline for the Next.js 16 port
• interactive-qa-post-web-ag-5 — Runtime findings, known issues to track

Accessibility and quality audit programme (April 2026)

A run of WEB-META-N specs hardened the rebuilt site for accessibility, security, and brand polish ahead of investor-readiness and DNS cutover. Specs and ship history live in pride-website/_specs/ and the codebase commit log; this is the abridged narrative for cross-project context.

• WEB-META-1 — pride-website/CLAUDE.md rewritten from 29 lines to 154, codifying 12 rules drawn from S1–S6 drift. See WEB-META-1 CLAUDE.md Level-Up.
• WEB-META-2 (shipped 2026-04-27, SHAs 949dc59 + 3e4aa7e) — Lint cleanup. ESLint scoped to app code, 19 explicit any types replaced with proper Sanity / Square types. Net 175 → 0 lint warnings.
• WEB-META-3 (shipped 2026-04-27, SHA 3d5cda6) — CSP hardening. All 11 fetch/navigation directives enumerated in next.config.ts. data: URIs allowed for grain-SVG noise overlays (closes the S6 gap). 'unsafe-eval' dropped — framer-motion v12 ships clean without it. Mozilla Observatory grade B+/80 (held by 'unsafe-inline' on script-src; nonce/hash CSP is a future spec).
• WEB-META-4 (shipped 2026-04-27, SHA 19339c0) — Brand contrast. Pink-on-cream #eb1478 on #fffaf7 (4.13:1, fail) replaced with --primary-dark #a1094f (7.59:1, AAA) on body text and the navigation CTA. Mid-execution Claude Code surfaced a parallel mobile-drawer instance (navigation.tsx:432) that Cowork’s audit grep had missed — caught and folded into the same ship.
• WEB-META-5 — Safari QA (Todo). Manual pass on macOS Safari + iOS Safari, owner Shae. 12-route × 2-browser matrix. Tracked as Linear WEB-32.
• WEB-META-6 (shipped 2026-04-27, SHA 71295f2) — Opacity-modifier audit (WCAG 1.4.3). 6 files lifted text-secondary/{40-55} → /70 (fail-body 3.79:1 → AAA 7.72:1). Closes the residual /contact, /merch, /functions text-contrast bugs surfaced in META-4’s Lighthouse runtime.
• WEB-META-7 (shipped 2026-04-27, SHA 031e0a7) — Pink-button surface swap. 7 files swept bg-primary → bg-primary-dark propagating the META-4 navigation pattern site-wide. Lifts 4.10:1 / 4.26:1 fails to 7.45:1 / 7.74:1 AAA. /merch and /cocktail-lounge Lighthouse mobile a11y move 96/1 → 100/0.
• WEB-META-8 (shipped 2026-04-27, SHA 81ad1ce) — Border contrast (WCAG 1.4.11). 8 files lifted form-input and interactive-chip borders to 3:1 minimum. Cream surfaces /20 → /75 (9.10:1 measured). Cocktail palette /15-/20 → /40 (3.35:1 measured) after Claude Code mid-execution surfaced an sRGB-vs-linear-Y compositing math error that the original spec hadn’t caught — corrected sRGB-aware math is now mandatory in audit-method standards.

Cumulative outcome (post-Session 21): all 9 audited routes at 100/0 Lighthouse mobile a11y, 0 SC 1.4.11 violations on modified critical-path components, 0 console errors / 0 CSP violations across 12-route smoke test.

Phase 2 deferred: comprehensive border-system token revision (~30+ files), semantic muted-text token introduction, nonce/hash CSP for Observatory A grade, button-surface canonicalisation. All filed as future WEB-META-N specs, prioritised by Shae.

Cross-project context

• humphrey — Humphrey shares tech stack (Next.js 16, Tailwind v4). Design tokens and patterns may flow between the two.
• wiki-viewer — The /invest/data-room page pattern should feel consistent with the Quartz viewer Mat uses.
• ops — Copy about kitchen, licence, and programming must track what’s actually happening operationally — check Ops sub-index before making forward-looking claims.
• finance — Financial figures on the site must be trends/percentages only. Absolute figures (Xero-sourced) stay gated.

Never-publish list (mirrors pride-website/CLAUDE.md)

• Personal phone numbers or individual emails → use contact forms and meet@prideofourfootscray.bar
• Absolute financial figures → trends and percentages only
• Investment terms before disclosure lodged with ASIC → Phase 2 only
• Individual shareholder data (names, holdings) → never public
• Tailwind dark: prefix → use [data-theme="dark"]

Recent updates

• 2026-04-27 (Session 22) — Added accessibility-and-quality audit programme section covering META-1 through META-8. WEB-META-5 ticketed as Linear WEB-32 (Todo). Memory’s stale Linear reference (PRD- in Pride Intelligence) corrected — current truth is WEB- in Pride Website team.
• 2026-04-27 (Sessions 19, 20, 21) — Seven WEB-META-N specs drafted; META-2/3/4/6/7/8 all shipped to prod main. Site moves from baseline accessibility (96/1 on /merch + /cocktail-lounge) to 100/0 mobile a11y on all 9 audited routes. CSP hardened to enumerated directives, lint clean, brand contrast at AAA, opacity-modifier and border-contrast violations cleared.
• 2026-04-24 — Sub-index created (WIKI-META-1)