Divide the packages by category in the left sidebar

[Sfshaza]

Perhaps:

COMMON LIBRARIES
dart:async
dart:core
etc

HTML LIBRARIES
dart:html
etc

I/O LIBRARIES
dart:io
etc

@kwalrath

[sethladd]

common to what? :)

[devoncarew]

Flutter has ~37 libraries in its main doc page now: http://docs.flutter.io/flutter/. We could benefit from some type of categorization. Perhaps something like --use-package-categories, which would roll-up the various libraries by the source package? That would help in our case.

[jcollins-g]

How is this different from --use-categories? It is a little wonky in edge cases but tries to do that.

[kwalrath]

Do we have docs/examples for --use-categories, @jcollins-g? I looked around but didn't find them.

The last time I looked into this, I wanted to be able to have arbitrary groupings of libraries (like the ones Shams proposed), and I couldn't figure out how to do it.

[jcollins-g]

http://docs.flutter.io uses --use-categories. Without it the left column on that page would be a flat list of libraries. It's generated by a script in flutter.

[jcollins-g]

Changes to the new dartdoc in 0.11.0 include a --category-order flag which can give you some control over where libraries appear, but it might not be quite what this is looking for.

[chalin]

So I believe that part (all?) of this has landed, judging from the looks of https://api.dartlang.org/dev:

Elsewhere, @kwalrath wrote:

I'm wondering if the API docs should label the top group... it's hard to describe which libraries you can use in web apps, except by saying "non-VM" (and vice versa). ...

The original comment of this issue suggested a category name ("Common") for the top-level group. Could we have a category name for this group? Maybe one of:

• Common or
• Core or
• Shared or maybe
• Cross-platform?

cc @kevmoo

[jcollins-g]

Looks like #1610 is a duplicate of this.

The current implementation is malleable; it's possible to for me to add a configuration option in dartdoc_options.yaml that defines the name of the default category.