Thanks for contributing to Rondo Club.
- Open an issue or discuss the change before large feature work.
- Keep pull requests focused. Small, reviewable PRs merge faster.
- Update documentation and the changelog when behavior changes.
- PHP 8.0+
- Node.js 18+
- Composer
- WordPress 6+
git clone git@github.com:RondoHQ/rondo-club.git
cd rondo-club
composer install
npm installStart the Vite dev server:
npm run devBuild production assets:
npm run buildLint JavaScript/JSX:
npm run lintRun PHP coding standards:
composer lintAuto-fix what PHPCS can fix:
composer lint:fixRun the wp-browser / Codeception wpunit suite:
composer testIf you add or change business logic, add or update tests in tests/Wpunit/.
- Follow existing naming and file structure conventions.
- Keep changes narrow and avoid unrelated refactors in the same PR.
- Prefer adding changelog entries under
## [Unreleased]inCHANGELOG.md. - For API or UI changes, include screenshots or a short explanation in the PR.
- For WordPress code, follow the rules in
phpcs.xml.dist.
Before opening a PR, make sure you have:
- run
npm run lint - run
composer lint - run relevant tests
- updated
CHANGELOG.mdwhen needed - updated docs/README if setup or behavior changed
PRs should clearly describe:
- what changed
- why it changed
- how it was tested
- whether any manual migration or deploy step is needed
Please do not report security issues in public GitHub issues. See SECURITY.md.