What Helps
- Documentation fixes with the affected page or file linked.
- Reduced reproductions for visual, keyboard, focus, or browser issues.
- Accessibility observations that name the device, browser, and assistive technology used.
- Focused component improvements that preserve Bootstrap markup and public behavior.
- Tests that lock public contracts without freezing incidental prose or DOM details.
Local Setup
1
2
3
4
5python3 -m venv .venv
.venv/bin/pip install -r requirements-dev.txt
env npm_config_cache=/private/tmp/wpmoo-npm-cache npm install
.venv/bin/python build.py
.venv/bin/python dev.py
Browse the local catalog at http://localhost:4173/.
Workflow
- Work from
dev; main is released through PRs.
- Keep each PR focused on one public concern.
- Do not mix docs copy, runtime behavior, release automation, and version bumps unless the release scope says so.
- Preserve package exports, public URLs, and the Core/Docs boundary unless the PR is explicitly about those contracts.
Core / Docs Boundary
Moo UI Core source and package outputs live outside site/;
dist/ is the npm package build. The site/
tree owns ui.wpmoo.org templates, catalog chrome, metadata, and
preview artwork. Internal Jinja macros are repository build tools, not
npm APIs.
Issue Types
Use the focused issue forms so reports carry the information needed for
review.
Private Reports
Do not report suspected vulnerabilities or private conduct concerns in
public issues. Use the repository security policy or the private
contact route listed by the WPMoo organization.