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.
In Architecture Without Architects, Bernard Rudofsky documented the ways in which most cities were mostly built by improvisation, following no consistent formal design. Building was added to building, street to street, their forms adapting to different site conditions in the process of extension.
Rudofsky thought that this hidden order is how most settlements of poor people develop and that the work of improvising street order attaches people to their communities, whereas 'renewal' projects, which may provide a cleaner street, pretty houses, and large shops, give the inhabitants no way to mark their presence on the space.