<p dir="auto">Desire: make docs.flutter.io an excellent resource for learning how to use Flutter.</p>
<p dir="auto">Challenge: for some domains (e.g. Input) that do not have their own library and cut across multiple libraries, we don't seem to have an easy way to author holistic docs. We'd like a "starting point" for a concept, one that is easy to identify when visiting docs.flutter.io.</p>
<p dir="auto">Strawman proposal: something like a <code class="notranslate">@category</code> that can be used to link various classes and libraries. We also need a way to say "this page is the home page for a <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/category/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/category">@category</a>"</p>
<p dir="auto">(I thought we had an issue open for this, but couldn't find it on either <a href="https://github.com/dart-lang/dartdoc/issues">https://github.com/dart-lang/dartdoc/issues</a> or flutter.io/issues)</p>
<p dir="auto">As we learn from UX studies, we noticed that we don't currently have an easy way for a developer to understand in which "area" they are looking at a concept. For example, if they are looking at the Padding class in the API docs, "where" are they? What kind of conceptual thing is this?</p>
<p dir="auto">From a current Flutter developer: "More broadly, a tricky part of onboarding was simply familiarizing with the wide range of specialized widgets. "</p>
<p dir="auto">(Note: our library organization in the framework is too coarse-grained to convey this grouping. For example, there are a lot of conceptual areas inside the widget library.)</p>
<p dir="auto">Vision: a user looking at a thing in the API docs should easily understand in which group/AreaOfInterest/Layer it belongs, and then easily see other related things. For example, when looking at Padding, the user can easily see "This is part of the <em>layout</em> area of interest. Oh, these are the other helpful layout ideas."</p>
<p dir="auto">Strawman: a way to annotate the thing (class/function/etc) to put it in a "doc grouping". Then, the dartdoc tool could be taught how to indicate which group the thing is in.</p>