that is not really true. you can have several documents. but as we talk *content*, its often just about display logic. so a simple controller that just selects the right template for a content and renders that template is usually enough.

apart from that, i fully agree with how you put it: the route is tied to a specific content, and resolving this link in a controller would be redundant. and awkward, as you *might* want to use a specific controller for some classes of documents.

if you see what i mean, can you try to rework this passage a bit? otherwise we can also wrap this up and merge, and i can do a PR on the merged thing afterwards to discuss further precisions. (and yes, you need to stop me from confusing people with too many details in the introduction :-) on the other hand, incorrect claims here will confuse users later)