Page class

Represents a documentation page. A page can contain subpages to represent nested documentation set structure.


Page.fromJson(Map _json)


content String
The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file.
read / write
hashCode int
The hash code for this object. [...]
read-only, inherited
name String
The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with .) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include ==) subpages: - name: Java content: (== include ==) You can reference Java page using Markdown reference link syntax: Java.
read / write
runtimeType Type
A representation of the runtime type of the object.
read-only, inherited
subpages List<Page>
Subpages of this page. The order of subpages specified here will be honored in the generated docset.
read / write


noSuchMethod(Invocation invocation) → dynamic
Invoked when a non-existent method or property is accessed. [...]
toJson() Map<String, Object>
toString() String
Returns a string representation of this object.


operator ==(Object other) bool
The equality operator. [...]