Working on *just* the UX?

I'd love to contribute to the UX, but setting up Elastic Search, Python3, Lua, and Apache or NGINX is a bit much to tweak some HTML and JS which gets it's "meaning" from a JSON API.

Would it be possible to either:
a) allow the UX to work against a remote API (i.e. test UX against https://lists.apache.org/)
b) mock the API (perhaps via an API documenting format like [OpenAPI](https://www.openapis.org/), [RAML](https://raml.org/), etc.)

Option A seems the simplest/fastest (assuming the API is or could be setup to enable CORS--see http://www.test-cors.org/).

The lower the bar is for contribution, the more designer/UX types (who likely don't have Elastic Search et al handily installed and running) might be able to help this project.

Just an idea! 💡
🎩

Start by mapping the UX HTML and JavaScript to the JSON API, then review the local setup requirements for Elastic Search, Python3, Lua, and Apache or NGINX. Compare the proposed remote API with CORS enabled against an OpenAPI-style mock; done means contributors can work on the UX without installing the full backend stack.

Written by the indexing model from the issue text.