A lightweight, mobile-first web app that helps Columbia Neighborhood Swim League (CNSL) swimmers, families, and fans quickly find information about pool openings, team practices, meets, and league resources.
Run the PowerShell developer menu for the usual setup, build, server, lint, test, PWA, and performance workflows:
.\start.ps1# Use Node.js 24 or newer from the checked-in baseline
nvm use
# Install dependencies
pnpm installThis project uses PostHTML for component-based HTML development. The source files are in the src/views directory and compiled to the /out directory.
# Build HTML files once
pnpm run build
# Build and watch for changes
pnpm startsrc/views/*.html- Source HTML files with PostHTML syntaxsrc/views/layouts/*.html- Layout templatessrc/views/components/*.html- Reusable componentssrc/css/- Stylesheetssrc/js/- JavaScript filessrc/assets/- Images, data files, and other static assets/out/- Build output directory (generated files for deployment)
Pools, meets, and teams are stored beneath annual domain folders in src/assets/data/<YEAR>/<domain>/. The active published season is selected by YEAR in src/js/config/app-config.js.
The non-seasonal swim lesson provider directory is maintained in src/assets/data/lessons.json. It contains factual provider and contact details but intentionally excludes pricing and schedules.
See Annual Season Assets for the exact PDF, JSON, and schema layout and the checklist for preparing a new season such as 2027.
The seasonal-source GitHub Actions workflow runs nightly during May, June, and July and can also be dispatched manually. It performs deterministic source requests, opens deduplicated review issues for candidate content differences, and may open a narrowly bounded pull request for metadata-only baseline refreshes. Deliberate semantic source reviews remain required before modeled data, source-review timestamps, or visitor-used destinations change. Begin each local review with pnpm run check:data-updates, reconcile its collected URLs with every official source defined by the active annual JSON and annual README, and directly request any uncovered source. Record every successfully completed review in the source check log, update the matching source-review timestamps, and refresh the accepted baseline with node scripts/season-data-agent.js --initialize. Structured JSON updates remain reviewed transcriptions of official material. Run pnpm run validate:data after annual-data changes as a separate integrity check; it does not prove that current online sources were reviewed. See Seasonal Data Source Review for the complete coverage and evidence requirements.
Extract searchable text from a retained PDF with the workspace-local Poppler WebAssembly tool. The command preserves the document's physical layout and writes LF line endings. It mirrors the retained evidence path beneath tmp/pdf-text/, keeping dated versions separate without writing text files into the annual source tree.
pnpm run extract:pdf -- src/assets/data/2026/pools/pool-schedules/krp/2026-06-17/Kendall_Ridge.pdfThis example writes tmp/pdf-text/2026/pools/pool-schedules/krp/2026-06-17/Kendall_Ridge.txt.
Run tests by naming only the files or browser IDs affected by your changes. Complete unit and browser suites run in CI; local broad-suite commands are for explicitly requested investigations only.
pnpm run lint
node --test tests/<area>/<affected-module>.test.js
node scripts/run-playwright.js test <affected-spec> --grep "<stable IDs>"
pnpm run validate:data
pnpm run build
pnpm run verify:pwaPlaywright browser verification is deferred to the Browser Verification GitHub Actions workflow. Each Sunday during May, June, and July, its scheduled check runs Chromium workflow and automated WCAG A/AA checks only when a push to main was recorded during the preceding seven days. It can also be run on demand through workflow dispatch. Browser results are reported separately and do not delay or block a GitHub Pages build. Use the Release Verification Checklist for the secure-origin installed-PWA and manual assistive-technology checks that automation cannot establish.
Design and maintenance decisions are recorded in the Visual Style Guide, Runtime And Stylesheet Ownership, Security And Privacy Decision, and retained Voice Assistant Question Scope.
This project uses GitHub Actions to automatically build and deploy the website to GitHub Pages when changes are pushed to the main branch. The workflow:
- Checks out the repository
- Sets up Node.js
- Installs dependencies
- Runs lint and unit-test checks
- Validates active annual data against its schemas and retained-source inventory
- Builds the project using PostHTML
- Verifies the generated PWA cache, offline, and publication metadata contract
- Uploads the built files as an artifact
- Deploys the artifact to GitHub Pages
Separately, the browser-verification workflow runs Playwright each Sunday during May, June, and July after a push to main in the preceding seven days, or when manually dispatched.
Workflow configurations are located in .github/workflows/build-deploy.yml and .github/workflows/browser-verification.yml.
Repository automation and Copilot configuration is kept in .github/:
.github/agents/contains discoverable GitHub Copilot custom agent profiles..github/automation/contains automation support files, operating notes, reports, and reviewed state for active and retired workflows..github/instructions/,.github/skills/, and.github/copilot-instructions.mdcontain repository-specific Copilot guidance..github/workflows/contains GitHub Actions definitions;.github/dependabot.ymlconfigures dependency update checks.
Automation references:
- Refactoring Audit documents the weekly assessment driven by the
refactoring-auditorcustom agent. - Seasonal Data Source Review documents the active nightly detector, required deliberate semantic review, and reviewed fingerprint baseline.
The separation of automation/ from agents/ keeps retained automation support files from being discovered as custom agent profiles.
- Mobile-friendly design with large, tappable buttons
- Team profiles with coaches and practice schedules
- Meet calendar with pool closures
- FAQs and league documents from official CNSL sources
- Installable Progressive Web App (PWA) with offline application-shell and seasonal directory caching
- Keyboard-friendly navigation, status announcements, and reduced-motion support
- Purpose-limited Google Analytics usage reporting on the deployed site, with advertising personalization disabled
- Hosted via GitHub Pages with custom domain and HTTPS
/CNSL
├── src/
│ ├── views/ # Source HTML files
│ │ ├── components/ # Reusable HTML components
│ │ └── layouts/ # HTML layout templates
│ ├── css/
│ │ └── styles.css # Site-wide responsive and accessible styles
│ ├── js/ # Browser controllers, models, services, and types
│ └── assets/ # Images, annual data, and visitor resources
├── scripts/ # Build, validation, and measurement tools
├── tests/ # Unit and browser verification
├── docs/ # Maintenance and product decision records
├── out/ # Generated deployment output (gitignored)
├── manifest.webmanifest # PWA configuration
├── service-worker.js # Offline asset caching
├── robots.txt / sitemap.xml # Published crawler metadata
└── README.md # Project overview and data sources
All content is built on publicly available resources from the Columbia Neighborhood Swim League:
This site is hosted via GitHub Pages:
- Repo: github.com/simonua/cnsl
- Live site: pools.longreachmarlins.org
Custom domain configured with GitHub DNS and secured with HTTPS.
Maintained by Simon Kurtz
Community-driven. Not affiliated with Columbia Association or CNSL.