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.
Choi: I love [this contemporary banana cream pie] because sometimes new presentations create that iconic or nostalgic thing, but then they don't taste like nostalgia. But this one tastes like a banana cream pie.
Puck: So many young chefs today forget that food has to be delicious. If it's not delicious, why do it? If it's just interesting, you go once, that's it – "okay, I get it, but I don't want to go back."
Choi: I hear you chef. That's what I teach my cooks. I say, "You can do anything you want, but if you can't beat a banana cream pie, then the banana cream pie still wins." In most cases they don't. They can't beat the original.