Trailz Update

It’s been a bit. But I can assure you we didn’t go on vacation. Quite the contrary.

Sam put on his white job-site helmet, rolled up the sleeves on his best gingham shirt, shimmied into his darkest pair of selvedge jeans and got to work architecting what will become our database. This will be where we store information that keeps track of the trails, steps, nodes and where the front-end requests that information from. Sam’s also working on the API to make them sing to each other in harmony. Our JSON structure will need to reflect the tree/node structure we’re currently working towards. Although we’ve been discussing the merits of other visualizations as well. Things that might lend themselves to the often chaotic nature of information gathering. We’re thinking that tree/node might be a little to straight forward.

(Side note: The vocabulary of what we’re doing is going to be important. Semantic clues are going to give the user a mental model of what’s going on. And the more clear the mental model, the less work they’ll have to do in order to start using the platform.)

I have been working on creating the Ux, front-end web development and learning d3.js, an extraordinary and powerful “data driven document” library that allows you create data visualizations like it ain’t no thang. Of course, that’s after you master it. At the current stage, I can confidently say that it is, in fact, a thang. But I’m getting there. And I’m enjoying it.

What we’re working towards is not the multi-view that we originally presented. That’s a long term goal. But for now we’ve condensed things down into a single view.


This will be easier to understand the first time someone encounters it. And it still invokes the functionality and utility that we originally set out to create.

Cover image from