This canonical issue tracks all of the symptoms, problems, struggles, and weirdness which result from design choices made in Angular's content projection functionality. The issues deduplicated here may at first glance seem like problems in their own right, but actually are consequences of the way content projection works today. Rather than apply bandaid fixes which might make the system even more complicated, we want to address these problems at their source, by improving the content projection design.