There is an embarrassment of riches. In any category of open source software where that’s true, evaluating the choices becomes an interesting challenge. Some useful criteria:
– Activity. Recent activity (commits, discussion, pull requests) by one or more contributors sends a strong positive signal.
– Demo. A live online demo, when feasible and if comprehensive, can help you decide whether to invest in exploring the project more deeply.
– Documentation. Clear, concise, and complete documentation also helps you decide whether to investigate more deeply.
– Size. Other things being equal, less code is more.
– Self-sufficiency. Other things being equal, less dependency on other code is more.
In my search for a JSON forms editor, these criteria led me to Jeremy Dorn’s json-editor. It’s small, self-contained, and wonderfully capable. And the demo is spectacular. Using it, I learned everything I needed to know about the tool, and verified that it met all my requirements. Because json-editor supports JSON schema, I was even able to prototype the data structures I was planning to use and then interact with them directly in the live demo.
Well done, Jeremy! You have not only created an excellent software tool. You have also exemplified how to present such a tool in a way that enables people to evaluate it quickly and thoroughly, then (if it meets the need) adopt it easily.