Trails is the upcoming main addition to ShiftSpace it is an an interface for mapping information in the world of ShiftSpace. the idea is that shifts (ShiftSpace annotations/interventions/user-generated-content) left on different pages will be trailed together into information maps. We have been drafting tons of mockups, trying to figure out how should it work, what would be compelling to use? What would be a way to sculpt Trails in a way that would facilitate the potential we see in it? What would be feasible to execute? What would be flexible enough to iterate on as we develop? and so on…