docs: Move M2 theming information into separate guide #29054
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amysorto
added
docs
amysorto
force-pushed
the
m3-docs-changes
branch
3 times, most recently
from
6f89f9d
to
bd4d25a
Compare
crisbeto
approved these changes
May 16, 2024
There was a problem hiding this comment.
LGTM once the comment around naming is addressed. Also should remember that the guides config in the docs app needs to be updated: https://github.com/angular/material.angular.io/blob/main/src/app/shared/guide-items/guide-items.ts
amysorto
added a commit
that referenced
this pull request
May 16, 2024
* docs: Move M2 theming information into separate guide * docs: Use updated API prefix in M2 guide (cherry picked from commit 3e19768)
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move the M3 theme guide into the theming guide and pull out the M2 information into it's own separate guide.
This does not include updating the the theming your own components guide and the typography guide. I figured I could do that in a follow up PR to not make this too large.