docs: add section about plugins options and improve examples in Motion UI docs #11435
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.
Description
The current documentation about Motion UI is not clear enough about how to use the animation classes with the Foundation plugins that support it. A simple example is given for
Toggler
, and people may think that others components like Reveal can be used the same way (it does not, see to foundation/motion-ui#123).This pull request add a section about the usage of Motion UI in the Foundation components with a list of the supported components and their options related to Motion UI. It also use a simpler example in the header section.
Changes
Screenshots (if appropriate):
Types of changes
functionality to change)
Checklist (all required):
develop
ordevelop-v...
).I have updated the documentation accordingly to my changes (if relevant).I have added tests to cover my changes (if relevant).