In #1459 @MarkLodato wrote
Group requirements into higher level abstractions to aid readability and ensure cohesion. It is much easier to understand if each level requires only one or two things with a clear name. The current RC1 has a seeming grab-bag of requirements that takes a fair amount of thinking to understand why it adds up to a whole.
Some of what's desired here may already be covered by the basics section of the spec that provides a high level overview of each level.
We could go further to combine more individual requirements but that can be quite tricky.
Ideally we can have a technical writer look into this.
In #1459 @MarkLodato wrote
Some of what's desired here may already be covered by the basics section of the spec that provides a high level overview of each level.
We could go further to combine more individual requirements but that can be quite tricky.
Ideally we can have a technical writer look into this.