[Auto-sync] Add new "TL;DR" component anywhere relevant (#2702) #2706
Conversation
This file contains hidden or 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
* Add TL;DR in quote at the beginning of each Cloud docs page * Add first draft of Tldr component with a very basic design * Create some Tldr example content in Preview feature page * Test different design variants * Try various design proposals * Add TL;DRs in most files of the CMS docs * Test simple design * Streamline Tldr component design * Use component in all pages where a tl;dr content was added * Add missing TL;DRs and fix a few mistakes --------- Co-authored-by: Mégane Lacheny <megane.lacheny@strapi.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Automatic sync of commit from main