Devani accepts contributions by email — no account to create, no fork ceremony. Every release ships as complete MIT-licensed source, so the code you download is the code you patch.
The loop
- Get the source — the latest release zip from devani.io/resources.
- Run it locally —
php -S localhost:8000(see Running locally & testing). - Make the change — match the surrounding style; keep it focused. One fix per patch beats a grab-bag.
- Test it — lint, the sanitizer suite if you touched the save path, and the actual flow you changed.
- Send it — email a diff (or the changed files) to hello@devani.io with a few sentences: what was broken or missing, what you changed, how you tested. If it fixes a bug, include reproduction steps.
What gets merged fast
- Bug fixes with a repro and a test (or a manual test recipe).
- Docs corrections — these get reviewed fastest of all.
- New editor blocks that follow the canonical classes and sanitizer conventions.
- Install recipes for stacks we don't run ourselves, verified on a real box.
What to talk about first
Anything architectural — new integrations, storage-format changes, MCP surface changes. Email the idea before writing five hundred lines; the maintainers can usually point at the right pattern (there's almost always an existing one) and save you a rewrite.
Security issues
Not this path. Email security@devani.io privately so a fix ships before details circulate. Reporters get credited in release notes if they want to be.
Terms
MIT in, MIT out — no CLA, no copyright assignment. Merged changes ship in the next release with credit to you in its notes.