- Update page title for each piece of documentation to use the vernacular concept rather
than the class name for the component.
- Treat all instances of class names as proper nouns and mark them as code names.
PiperOrigin-RevId: 155705022
I'm updating this CL as I go to fix all the issue we can find.
* Icon lists items now use correct icons, and are rearranged to be consistent.
* Removed HTML comments that were interfering with the Liquid templates.
* Added the benefits list to the docsite-index.
* Capitalized "Design" in Material Design.
* Spec links in icon list now use consistent labels.
* URLs, headings and page titles are now internally consistent within the platform.
PiperOrigin-RevId: 155445665
Follows these rules:
Title is the Component Name as it appears in spec.
Justification: Formatting and display on small width screens.
Excerpt includes the CamelCase name of the java class.
Justification: This document is not a rehash of spec, it's a specific resource for Android devs. Title and excerpt are displayed in the same context.
Header is the CamelCase name of the java class.
Justification: Similar to excerpt. This is documentation on a specific Android widget.
Path is the dash-deliminated name of the java class.
Justification: Similar to header. This is documentation on a specific Android widget.
PiperOrigin-RevId: 155134932
