Contact

Where to reach us

There is no ticketing system and no support contract — just an inbox and a repository. Messages are read, and replies come when they can.

• [email protected]Email, for anything that does not belong in public
• GitHub repositorySource code, releases and discussion
• GitHub issuesBug reports and feature requests, tracked in the open

Reporting a bug

The useful details are your browser and version, what you did, what you expected, and what happened instead. A small document that reproduces the problem helps more than anything else — please reduce it to the smallest example that still fails, and never send real customer data or credentials.

Requesting a feature

Describe the task you are trying to finish rather than the button you have in mind. Knowing the workflow usually leads to a better answer than the feature as first described, and it makes it clear whether the idea belongs in a JSON editor at all.

General feedback

Anything that felt slow, confusing, or wrong is worth sending, however small. Notes about keyboard behaviour, screen readers and unusual documents are especially welcome, because those are the things that are easiest to miss.