Skip to content

Add elevation guide #2800

Closed
Closed
@Splaktar

Description

@Splaktar

Bug, feature request, or proposal:

proposal

What is the expected behavior?

That .md-elevation-zX classes 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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsThis issue is related to documentationfeatureThis issue represents a new feature or feature request rather than a bug or bug fixhelp wantedThe team would appreciate a PR from the community to address this issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions