Contributing a use case

This site tracks real projects people have built with Jev. A "use case" entry is one specific project: something someone actually shipped, with a real description of how it calls Jev. Not a marketing claim, not a plan — something that exists.

There are two ways to add one.

The form (fastest)

Go to jevusecases.com/submit and fill it in. It opens a pull request here automatically with your entry. You don't need to touch this repo directly.

Open a pull request by hand

Use this path if you'd rather fill in more of the researched fields yourself (a benchmark number, a replaces verdict), or you just prefer working in a PR over a form.

1. Fork this repo.
2. Copy TEMPLATE.jsonc. It's one fully-annotated example entry — every field explained inline, with the // comments stripped before it goes into real JSON.
3. Fill in your own values. Only fill in what you can honestly say is true — leave everything else null. An entry with most fields null is normal; that's what a freshly-added, not-yet-researched entry looks like, not something to apologize for.
4. Save it as src/data/entries/<your-id>/entry.json, where <your-id> matches the id field you filled in (e.g. src/data/entries/yourhandle-your-project/entry.json). Every entry gets its own folder — this is a new file, not an edit to an existing one, so your PR won't conflict with someone else's unless you both happen to pick the exact same id. Using your handle as the prefix (as the template does) makes that collision unlikely. Run npm test to check the entry: if a field is missing or wrong, the error names it.
5. Open a pull request against main.