-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add new "TL;DR" component anywhere relevant #2702
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
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
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pwizla
added a commit
that referenced
this pull request
Sep 16, 2025
* 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 <[email protected]>
pwizla
added a commit
that referenced
this pull request
Sep 17, 2025
* 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 <[email protected]>
This was referenced Oct 8, 2025
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
internal
PRs created by the Strapi core team
pr: new content
PRs for new product features or new documentation sections
source: repo
PRs/issues not targeting a specific documentation but rather affecting the whole repo
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.
This PR groups #2699 and #2700 into one, and adds the
<Tldr>
component from #2694 to the mix, with an updated, simplified design.