Dover Run Club - NH Running Community

Dover Run Club Website Product Brief

Dover Run Club Website Product Brief

Purpose

Provide a simple, welcoming web presence for Dover Run Club that answers the essentials quickly: what the club is, when it meets, where to show up, and what the vibe is.

Product Goals

  • Make first-time visitors confident enough to join a Tuesday run.
  • Keep Phase 1 maintenance low with a single-page-first approach.
  • Preserve GitHub Pages compatibility and lightweight Jekyll delivery.
  • Create a clear foundation for future expansion without exposing unfinished content.

Target Users

  • New local runners looking for a low-pressure group.
  • Returning members checking weekly run details.
  • Friends/community members validating club basics before attending.

Current Scope (Phase 1)

  • Public experience centers on the homepage only.
  • Homepage communicates:
    • What: Dover Run Club (casual, social group)
    • When: Tuesdays at 6:00 PM
    • Where: The Brick, Dover, NH
    • Vibe: All paces welcome; social post-run hang
  • Additional pages may exist in-repo for future phases but remain unlinked in main navigation.

Non-goals

  • No multi-page information architecture in navigation yet.
  • No formal membership system, dues workflow, or account features.
  • No heavy framework adoption or redesign away from current custom CSS + Jekyll setup.
  • No publishing placeholder content as primary user paths.

Tone

Casual, welcoming, and inclusive. Clear language, low friction, and community-first voice aligned with: “We run and then we pub, in that order.”

Success Criteria

  • Visitors can identify What/When/Where/Vibe within seconds on first load.
  • Main navigation stays focused on Phase 1 scope (single-page-first).
  • Content updates remain simple for maintainers (Markdown + lightweight templates).
  • Site builds and deploys cleanly via GitHub Pages-compatible configuration.

Agent Guardrails

  • Keep changes focused and minimal; avoid unrelated refactors.
  • Preserve GitHub Pages/Jekyll compatibility.
  • Use existing design tokens/variables and current styling approach.
  • Keep hidden future pages unlinked from main navigation until explicitly promoted.
  • When structure/scope changes, update roadmap documentation in lockstep.

Roadmap Linkage

Phase progression and activation criteria for future pages are tracked in design/website-roadmap.md. This PRODUCT.md defines Phase 1 intent; roadmap entries define when and how scope expands.