-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Add elevation guide #2800
Copy link
Copy link
Closed
Labels
docsThis issue is related to documentationThis issue is related to documentationfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issueshelp wantedLabel noting an issue which the team is looking for contribution from the community to fixLabel noting an issue which the team is looking for contribution from the community to fix
Description
Metadata
Metadata
Assignees
Labels
docsThis issue is related to documentationThis issue is related to documentationfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issueshelp wantedLabel noting an issue which the team is looking for contribution from the community to fixLabel noting an issue which the team is looking for contribution from the community to fix
Type
Fields
Give feedbackNo fields configured for issues without a type.
Bug, feature request, or proposal:
proposal
What is the expected behavior?
That
.md-elevation-zXclasses are documented.What is the current behavior?
No documentation exists other than within closed PR and issue comments. There are some design documents, but they aren't really designed for developers using the APIs.
What is the use-case or motivation for changing an existing behavior?
To avoid repeated questions and rejected PRs like #2212.
Is there anything else we should know?
I would like to help with this documentation, but I would like some feedback on how the team would like this to be done before I submit a PR.
Should there be a separate doc/guide for elevation that covers examples of multiple components?
Should there be examples of using elevation in each component that it applies to?
Is there a list of such components?