Recently I've been revisiting projects (such as this) to expand their mission to support mobile (responsively), update based on evolving best practices, and more. It seems that building for "mobile first" is easier when you are starting from zero, but of course many projects have evolved over time to incorporate technology improvements as they mature; those cases can be more work to retrofit without breaking the original mission goals. That said, each project I've revisited has been really fun to rediscover and work through--web development has been a thing now for twenty years or so now and running in to code from various waypoints along that journey is a joy--even when you wince at some of it. :-)
I have been disappointed to find that it's sometimes difficult to communicate the benefits and process, which I consider to be a personal failing rather than a problem with the concept. I hope to learn to overcome this with more practice. I thought I'd add it here as a reminder to begin assembling some examples that illustrate pieces of the approach, and to help me organize a personal effort to communicate the pros and cons better.
An example building a table using a renderer to consume a JSON data structure shows a simple example of how to begin constructing an engine to build UI through data discovery. While the example uses static data, by simply interpolating the values via JSP, Mason, TT, or your preferred variable substitution language, or by returning the JSON in an AJAX response its easy to see how this technique is used to build user interface to provide a visitor with access to the data. This shows a readonly table, but the concept easily scales to accommodate dynamic form generation. Thinking bigger, imagine informing games, utilities, educational resources, etc. with a similar practice.
Back to top