Contribute to Awesome Jev

Help a developer make one focused, evidence-backed contribution to Awesome Jev. Produce a useful proposal that follows the repository's current rules; acceptance belongs to its maintainers.

Establish the contribution

Identify the project URL or local path, its Jev-specific benefit, and the requested outcome: review, prepare a patch, or submit. Infer these from the conversation and source; ask only for missing information that affects the result. Confirm affiliation and commercial relationships without guessing them.

Choose the appropriate route:

• External project or starter kit: propose a concise link in the closest existing README category. Keep its code in its own repository. A starter kit does not have to be copied into Awesome Jev to qualify.
• Code contributed to Awesome Jev: use examples/ for a small teaching workflow or the existing projects/ conventions for a more complete tool. Apply the repository's example requirements to either, scaled to the contribution.
• Existing entry: make a focused correction or update instead of adding a duplicate.

Use the user's requested route when it fits. Do not turn a listing request into an application rewrite or impose this repository's Python tooling on an external project.

Read the current rules

In an Awesome Jev checkout, read its AGENTS.md, CONTRIBUTING.md, README.md, docs/maintaining.md, and the applicable submission template. Otherwise retrieve their current contents from these canonical sources: