Water Systems Bench is an English-language, global workflow hub for sizing, checking, troubleshooting and planning real-world water systems from source to use.
- Domain: watersystemsbench.com
- Repository: github.com/canghun13/watersystemsbench
- Contact: canghun13@naver.com
- GA4:
G-7FB08YPX7C - Stack: static HTML, CSS and vanilla JavaScript
- Deployment: GitHub Pages with Cloudflare
The complete first-wave scope and one validated expansion cluster are implemented: 74 public HTML pages comprising 7 core pages, 5 connected system hubs, 37 working tools, 16 guides and 9 references.
The five workflows are:
- Pumps, Pressure & Pipe Flow
- Wells, Storage & Rainwater
- Irrigation & Sprinkler Systems
- Water Treatment & Water Quality
- Greywater Reuse Planning
The Water Treatment & Water Quality cluster starts at /systems/water-treatment-quality/. Its eight tools use tested or user-supplied values, show their methods and limitations, and do not claim potable-water safety, regulatory compliance or an approved design.
The Greywater Reuse Planning cluster starts at /systems/greywater-reuse/. Its five tools connect measured household supply, ET-based landscape demand, laundry event distribution, receiving-basin capacity and user-entered economics without approving a source, end use, potable connection or local compliance.
The site uses the Hydraulic Field Bench design system, SI-first calculations with common US customary units, unique metadata and canonical URLs, JSON-LD, breadcrumbs, GA4, sitemap, robots and llms.txt.
Node.js 20 or later is required.
npm run generate
npm run serveIn another terminal:
npm run qa
npm run verify:calculations
npm run qa:browsernpm run generate refreshes committed HTML and machine-readable site files. npm run qa:browser validates the latest recorded real-browser run in tools-qa/browser-results.json; update that report only after a new complete browser run.
Before changing the site, confirm the checkout, origin, active branch, working-tree state and latest commit, then read handover.md. Preserve user-managed content and unrelated changes.
Before finishing, inspect the diff, run relevant calculation/static/navigation/browser checks, update the operational documentation, commit, push main, and confirm local HEAD equals origin/main.