Open source works because of you.
Devani is built in the open by people who'd rather use a tool they helped shape than rent one from a vendor. Whether you write code, write docs, file bugs, or just tell people about it — there's a way in for every kind of skill.
You don't have to write code.
Some of the most valuable contributions to Devani aren't pull requests. Here are the six things that move the project forward, in rough order of how often we wish more people did them.
Bug reports
The single most useful thing a non-developer can do. A good repro, expected behavior, actual behavior, browser, and any console errors — that's gold.
Docs
Fix a typo, clarify a confusing section, add an example, write a missing page. Docs PRs get merged faster than code PRs.
Code
Pull requests welcome for bug fixes, new blocks, editor improvements, and integrations. Look for issues tagged good-first-issue if you're new.
Feature ideas
Open a discussion, not a 12-paragraph spec. The patterns we ship come from the third or fourth time someone asks for something — not from a PRD.
Show your work
Built a site on Devani? Add it to the showcase. We collect real examples, link to them, and learn from how people are actually using the tool.
Sponsor
If Devani saves you the cost of a WordPress stack, consider sponsoring. Even a few dollars a month keeps the project sustainable and independent.
From clone to merged.
If you've never contributed to an open-source project before, this is the path. Six steps, about an hour of work end-to-end for a small change.
- Fork the repo. One click on GitHub. You now have your own copy.
- Clone & install.
git clone, thennpm install. Should be the only setup needed. - Run locally.
npm run devspins up Devani onlocalhost:3000with hot reload. - Pick an issue. Filter for
good-first-issue. Comment to claim it so no one duplicates your work. - Make the change. Branch off
main, commit, push. The contributing guide explains commit message format. - Open the PR. Reference the issue. CI runs automatically. We'll review within a few days, usually faster.
$ git clone git@github.com:you/devani.git
$ cd devani
$ npm install
$ npm run dev
# Edit, commit, push, open PR. Done.
The honest shopping list.
If you're looking for high-impact contributions, these are the areas where extra hands move the project forward most. None of these are easy. All of them matter.
Accessibility
Keyboard navigation in the editor, screen-reader announcements for AI edits, color-contrast checking for theme presets. WCAG expertise welcome.
Internationalization
Translating the editor UI, supporting RTL languages, multilingual page tooling. We have stub support; we need depth.
Deploy recipes
Verified, working deploy paths for hosts we don't use ourselves — Render, Cloudflare Workers, Coolify, CapRover. Real-world testing > theoretical docs.
Block library
More built-in blocks: testimonials, pricing tables, FAQ accordions, comparison sliders. Each one a self-contained, well-tested component.
Tests
Coverage is okay; integration tests for the editor are thin. End-to-end tests for the AI editing flow would be especially valuable.
Migration scripts
We won't build a deterministic WordPress importer, but well-tested helpers — extract posts, rewrite shortcodes, normalize media — would help everyone using Claude to migrate.
How we say thanks.
No CLA, no contributor licensing weirdness, no "we own your work" clauses. Just the standard MIT terms and these small things.
- Credit in release notes. Every merged PR gets a line in the release that ships with it. Your handle, the change, a link.
- Contributor page. A list of everyone who's ever had a PR merged, generated from the Git history.
- Maintainer track. Consistent contributors get review rights, triage rights, and a say in roadmap.
- Conference reimbursement. If you're presenting on Devani at a conference and the project can afford it, we'll cover travel.
- Real references. If you're job hunting and need a reference for your Devani work, we'll write one.
The short version.
Be kind. Assume good intent. Disagree without being a jerk. Don't make the project a worse place than you found it. The full code of conduct is the standard Contributor Covenant, lightly edited — it lives in CODE_OF_CONDUCT.md in the repo.
The thing about open source is, nobody owes anybody anything. Which means every time someone files a thoughtful bug or sends a clean PR, it's actually a gift. We try to remember that.
Ready to dig in? The repo's open.
Pull the code, find an issue that looks interesting, and get started. We'll meet you halfway.