Add new "TL;DR" component anywhere relevant (#2702) (#2706)

* 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]>

Author: pwizla

docusaurus/docs/cloud/account/account-billing.md

@@ -14,7 +14,11 @@ tags:
 
 import InvoiceStatus from '/docs/snippets/invoices-statuses.md'
 
-# Account billing & invoices 
+# Account billing & invoices
+
+<Tldr>
+Billing details and invoices are managed on the Profile page, where payment methods are updated and invoice history is available.
+</Tldr>
 
 Through the *Profile* page, accessible by clicking on your profile picture on the top right hand corner of the interface then clicking on **Profile**, you can access the [<Icon name="credit-card" /> *Billing*](#account-billing) and [<Icon name="invoice" /> *Invoices*](#account-invoices) tabs.
 

docusaurus/docs/cloud/account/account-settings.md

@@ -15,6 +15,10 @@ pagination_next: cloud/account/account-billing
 
 # Profile settings
 
+<Tldr>
+Settings of the Profile page include account details, connected accounts, and account deletion options.
+</Tldr>
+
 The *Profile* page enables you to manage your account details and preferences. It is accessible by clicking on your profile picture, on the top right hand corner of the interface, and **Profile**.
 
 There are 3 tabs available in the *Profile* interface: <Icon name="faders" /> [*General*](#general), <Icon name="credit-card" /> *Billing* and <Icon name="invoice" /> Invoices (the last 2 are documented in the [Account billing details](/cloud/account/account-billing) section of this documentation).

docusaurus/docs/cloud/advanced/database.md

@@ -15,6 +15,10 @@ pagination_next: cloud/advanced/email
 
 # Database
 
+<Tldr>
+Default PostgreSQL can be swapped for any supported SQL database by aligning configuration and environment variables.
+</Tldr>
+
 Strapi Cloud provides a pre-configured PostgreSQL database by default. However, you can also configure it to utilize an external SQL database, if needed.
 
 :::prerequisites

docusaurus/docs/cloud/advanced/email.md

@@ -14,6 +14,10 @@ tags:
 
 # Email Provider
 
+<Tldr>
+Third‑party email services integrate through plugins and environment variables to replace the default sender.
+</Tldr>
+
 Strapi Cloud comes with a basic email provider out of the box. However, it can also be configured to utilize another email provider, if needed.
 
 :::caution

docusaurus/docs/cloud/advanced/upload.md

@@ -16,6 +16,10 @@ tags:
 
 # Upload Provider
 
+<Tldr>
+External storage like S3 or Cloudinary requires plugin setup, security middleware, and Cloud variables.
+</Tldr>
+
 Strapi Cloud comes with a local upload provider out of the box. However, it can also be configured to utilize a third-party upload provider, if needed.
 
 :::caution

docusaurus/docs/cloud/cli/cloud-cli.md

@@ -9,7 +9,11 @@ tags:
 pagination_next: cloud/advanced/database
 ---
 
-# Command Line Interface (CLI) <NewBadge />
+# Command Line Interface (CLI)
+
+<Tldr>
+CLI commands handle login, project deploy, linking, listing, and logout without needing a remote repository.
+</Tldr>
 
 Strapi Cloud comes with a Command Line Interface (CLI) which allows you to log in and out, and to deploy a local project without it having to be hosted on a remote git repository. The CLI works with both the `yarn` and `npm` package managers.
 

docusaurus/docs/cloud/getting-started/caching.md

@@ -10,6 +10,10 @@ tags:
 
 # Caching & Performance
 
+<Tldr>
+Edge caching via Cache-Control headers reduces latency and server load for heavy static content.
+</Tldr>
+
 For Strapi Cloud applications with large amounts of cacheable content, such as images, videos, and other static assets, enabling CDN (Content Delivery Network) caching via the <ExternalLink to="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control" text="`Cache-control` header"/> can help improve application performance.
 
 CDN caching can help improve application performance in a few ways:

docusaurus/docs/cloud/projects/collaboration.md

@@ -12,6 +12,9 @@ tags:
 
 # Collaboration on projects
 
+<Tldr>
+Project owners invite maintainers through the Share button, manage pending invitations, and revoke access.
+</Tldr>
 
 Projects are created by a user via their Strapi Cloud account. Strapi Cloud users can share their projects to anyone else, so these new users can have access to the project dashboard and collaborate on that project, without the project owner to ever have to share their credentials.
 

docusaurus/docs/cloud/projects/deploys-history.md

@@ -14,6 +14,10 @@ tags:
 
 # Deployment history and logs {#deploy-history-and-logs}
 
+<Tldr>
+Deployments tab lists every build with status and allows deep inspection of build and runtime logs.
+</Tldr>
+
 For each Strapi Cloud project, you can access the history of all deployments that occurred and their details including build and deployment logs. This information is available in the *Deployments* tab.
 
 ## Viewing the deployment history {#viewing-deploy-history}

docusaurus/docs/cloud/projects/deploys.md

@@ -15,6 +15,10 @@ pagination_next: cloud/projects/deploys-history
 
 # Deployments management
 
+<Tldr>
+Deployment triggers can be manual or automatic on git pushes, with the ability to cancel active builds from dashboard or CLI.
+</Tldr>
+
 The creation of a new Strapi Cloud project automatically trigger the deployment of that project. After that, deployments can be:
 
 - manually triggered whenever needed, [from the Cloud dashboard](#triggering-a-new-deployment) or [from the CLI](/cloud/cli/cloud-cli#strapi-deploy),