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:
<pre><code>pages:
name: Tutorial
content: (== include tutorial.md ==)
subpages:
name: Java
content: (== include tutorial_java.md ==)
</code></pre>
You can reference Java page using Markdown reference link syntax:
[Java][Tutorial.Java].
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["The `Page` class represents a documentation page and supports nested structures through subpages."],["Each page has a `Name` for identification and URI generation, and `Content` to hold the Markdown text of that page."],["The `Page` class can be constructed using a default constructor or by copying an existing `Page` object."],["The `Page` class contains three fields which are `ContentFieldNumber`, `NameFieldNumber`, and `SubpagesFieldNumber`, which refer to the fields content, name and subpages, respectively."],["The `Page` class supports methods for cloning, equality checks, calculating size, merging data, and converting to string, and is part of the Google.Api namespace."]]],[]]
