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.
# 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.
See Annual Season Assets for the exact PDF, JSON, and schema layout and the checklist for preparing a new season such as 2027.
Automated seasonal-source monitoring has been retired and does not run from GitHub Actions. Structured JSON updates remain reviewed transcriptions of official material. Run pnpm run validate:data after annual-data changes to validate active schemas, references, URLs, and retained official source documents. See Retired Seasonal Data Source Monitor for retained coverage notes and local investigation guidance.
pnpm run lint
pnpm test
pnpm run test:coverage # Delivered JS coverage; excludes maintenance implementations in scripts/
pnpm run validate:data
pnpm run build
pnpm run verify:pwaPlaywright browser verification is deferred to the Nightly Browser Verification GitHub Actions workflow. Each day 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 24 hours. 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 Runtime And Stylesheet Ownership and Security And Privacy Decision.
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 May-to-July daily browser-verification workflow runs Playwright after a push to main in the preceding 24 hours, or when manually dispatched.
Workflow configurations are located in .github/workflows/build-deploy.yml and .github/workflows/nightly-browser-verification.yml.
Repository automation and Copilot configuration is kept in .github/:
.github/agents/contains discoverable GitHub Copilot custom agent profiles..github/automation/contains retained notes and reviewed state for retired automations..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.
Retired automation references:
- Refactoring Audit retains design notes for the retired assessment driven by the
refactoring-auditorcustom agent. - Seasonal Data Source Monitor retains source-monitoring notes and its reviewed fingerprint baseline; no Actions workflow invokes it.
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
├── index.html # Season overview homepage (generated)
├── pools.html # Pool directory with filters (generated)
├── teams.html # Team cards and practice info (generated)
├── meets.html # Meet schedule with closures (generated)
├── faq.html # CNSL documents and policies (generated)
├── src/
│ ├── views/ # Source HTML files
│ │ ├── components/ # Reusable HTML components
│ │ └── layouts/ # HTML layout templates
│ ├── css/
│ │ └── styles.css # Site-wide responsive and accessible styles
│ └── js/
│ ├── pool-browser.js # Pool browser functionality
│ ├── teams-browser.js # Team browser functionality
│ └── meets-browser.js # Meet schedule functionality
├── manifest.webmanifest # PWA configuration
├── service-worker.js # Offline asset caching
├── robots.txt / sitemap.xml # Published crawler metadata
├── README.md # Project overview and data sources
└── assets/
├── images/ # Logos and icons
└── data/ # JSON for pools, teams, and meets
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.