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.
Since tall buildings have been around, there have been many ways they’ve fit into cities: towers in downtown, towers in the park, and most recently, towers on a whole-block development. Let’s look at a 4th way, the Tower in the Village.
Unlike the others, the Tower in the Village does not aim to be the center of attention. Instead, the upper floors are hidden behind a low front that fits in with the rest of the block. It faces a village green instead of a busy road.
Why highrise infill? Growing cities have two choices: 1) Redevelop a lot of sites to medium density, or 2) Redevelop a small number of sites to very high density. Highrise infill requires less demolition and can get more homes built faster.