BigBlueHat opened a new issue #468: 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
   b) mock the API (perhaps via an API documenting format like 
[OpenAPI](, [RAML](, etc.)
   Option A seems the simplest/fastest (assuming the API is or could be setup 
to enable CORS--see
   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! 💡 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to