Create separate HTML pages for each type.

utils/dartdoc/README.txt

 Dartdoc generates static HTML documentation from Dart code.
 
 To use it, from this directory, run:
 
     $ dartdoc <path to .dart file>
 
-This will create a "docs" directory with the docs for your libraries. To do so,
-dartdoc parses that library and every library it imports. From each library, it
-parses all classes and members, finds the associated doc comments and builds
-crosslinked docs from them.
+This will create a "docs" directory with the docs for your libraries. The
+easiest way to preview your generated docs is to spin up a little web server,
+like:
+
+    $ python -m SimpleHTTPServer
+
+Then point your browser at `localhost:8000` to see your magnificent creation.

[sethladd, 2011/12/01 04:50:33]

Probably don't need this anymore.

[Bob Nystrom, 2011/12/02 19:40:55]

Done.

+
+
+How docs are generated
+----------------------
+
+To make beatiful docs from your library, dartdoc parses it and every library it

[pquitslund, 2011/12/01 23:29:54]

beatiful -> beautiful

[Bob Nystrom, 2011/12/02 19:40:55]

Done.

+imports (recursively). From each library, it parses all classes and members,
+finds the associated doc comments and builds crosslinked docs from them.
 
 "Doc comments" can be in one of a few forms:
 
     /**
      * JavaDoc style block comments.
      */
 
     /** Which can also be single line. */
 
     /// Triple-slash line comments.
@@ skipping 42 matching lines @@
 
 There is also an extension to markdown specific to dartdoc: A name inside
 square brackets that is not a markdown link (i.e. doesn't have square brackets
 or parentheses following it) like:
 
     Calls [someMethod], passing in [arg].
 
 is understood to be the name of some member or type that's in the scope of the
 member where that comment appears. Dartdoc will automatically figure out what
 the name refers to and generate an approriate link to that member or type.