Skip to content

Conversation

pwizla
Copy link
Collaborator

@pwizla pwizla commented Sep 10, 2025

This PR groups #2699 and #2700 into one, and adds the <Tldr> component from #2694 to the mix, with an updated, simplified design.

Copy link

vercel bot commented Sep 10, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
documentation Ready Ready Preview Comment Sep 16, 2025 4:33pm

@github-actions github-actions bot added the internal PRs created by the Strapi core team label Sep 10, 2025
@pwizla pwizla self-assigned this Sep 10, 2025
@pwizla pwizla added source: repo PRs/issues not targeting a specific documentation but rather affecting the whole repo pr: new content PRs for new product features or new documentation sections labels Sep 10, 2025
@pwizla pwizla added this to the 6.9.0 milestone Sep 10, 2025
@meganelacheny meganelacheny marked this pull request as ready for review September 15, 2025 14:51
@meganelacheny meganelacheny self-requested a review as a code owner September 15, 2025 14:51
@meganelacheny meganelacheny self-assigned this Sep 15, 2025
@pwizla pwizla merged commit c896350 into main Sep 16, 2025
3 of 4 checks passed
@pwizla pwizla deleted the repo/tldr-everywhere branch September 16, 2025 16:31
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]>
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants