Embracing design constraints
Constraints have been shown to generally improve innovation. Giving targets and parameters helps ensure a team is working in unison. Identifying what is out of bounds can further focus that team.
Constraints have been shown to generally improve innovation. Giving targets and parameters helps ensure a team is working in unison. Identifying what is out of bounds can further focus that team.
What I sense is a real tension between the web as we know it, and the web as it would be. It’s the tension between an existing medium, the printed page, and its child, the web. And it’s time to really understand the relationship between the parent and the child, and to let the child go its own way in the world.
Generally speaking (and ignoring questions of styling, API availability, etc.), an ideal Web annotation pattern follows these principles:
- Annotations appear in close visual proximity to the primary content.
- Their design neither distracts from nor hides the primary content.
- The preceding principles are followed regardless of screen width.
The only pattern I’ve found that meets these criteria is FiveThirtyEight’s.
...As it turns out, FiveThirtyEight didn't invent this pattern. It likely originated in medieval illuminated manuscripts which contain “interleave notes” — comments written literally between the lines.
A rain chain in winter; Dresden Kunsthof Passage; Drainage planters near Pike Place Market in Seattle.
If there is a larger takeaway here perhaps it is about paths of least resistance, with regards to both the actual flow of water and design decisions. On the one hand, it is easy to blindly follow regional precedents and traditions with long histories (or grab whatever is handy at the hardware store). On the other hand, sometimes it makes sense to take a step back and decide consciously how to reveal (or conceal) a natural process.