Don't point people to pub-generated API docs

[kwalrath]

As discussed in #242, the pub-generated angular_components API docs are confusing because they contain so many libraries (most of which have no description, to boot). It's OK to generate the API docs, and maybe they should be hosted on pub instead of on webdev.dartlang.org, but we should encourage people to use the docs in the gallery instead. We can do this using the angular_components pubspec.yaml and README.

Some possible solutions:

• In the angular_components pubspec.yaml:
  • Keep the current homepage, but make docs point to the gallery:
    • homepage: https://webdev.dartlang.org/components (works no matter what the version is)
    • documentation: https://dart-lang.github.io/angular_components_example
  • Make the gallery the homepage, make docs point to the API doc homepage on webdev:
    • homepage: https://dart-lang.github.io/angular_components_example
    • documentation: https://webdev.dartlang.org/api?package=angular_components (this won't work until we switch the website to be v5)
• In the angular_components README:
  • Explicitly say that instead of using the auto-generated API docs, they should use the gallery, where they can see the running components and example code side-by-side. A screenshot of the gallery might be a good way to drive this home.
  • I could help with the README description.

/cc @chalin @kevmoo @TedSander @nshahan @isoos @jakobr-google @mit-mit @matanlurey

[nshahan]

• Keep the current homepage, but make docs point to the gallery:
  • homepage: https://webdev.dartlang.org/components (works no matter what the version is)

What do you mean about the versioning here? Is this link always to the stable version?

[nshahan]

Decided:
Homepage -> https://webdev.dartlang.org/components
Docs -> https://webdev.dartlang.org/api?package=angular_components