Skip to content

Commit cdd366f

Browse files
committed
Replaced mermaid diagrams with videos
1 parent bd6c8a0 commit cdd366f

File tree

5 files changed

+32
-52
lines changed

5 files changed

+32
-52
lines changed

src/content/docs/speed/optimization/content/compression.mdx

Lines changed: 6 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -9,32 +9,19 @@ head:
99
content: Content compression | Brotli
1010
---
1111

12-
import { Render } from "~/components";
12+
import { Stream, Render } from "~/components";
1313

1414
Cloudflare compresses content in two ways: between Cloudflare and your website visitors and between Cloudflare and your origin server.
1515

1616
## Compression between Cloudflare and website visitors
1717

1818
In addition to Cloudflare's [default caching behavior](/cache/concepts/default-cache-behavior/), Cloudflare supports Gzip, Brotli, and Zstandard compression when delivering content to website visitors.
1919

20-
```mermaid
21-
flowchart LR
22-
accTitle: Compressed responses sent to website visitor
23-
accDescr: Cloudflare can send responses to visitors using Gzip compression, Brotli compression, or no compression.
24-
25-
A[Visitor browser]
26-
B((Cloudflare))
27-
C[(Origin server)]
28-
29-
A == "Request" ==> B -.-> C
30-
C -.-> B == "Response<br>(Gzip / Brotli / Zstandard / No compression)" ==> A
31-
32-
style A stroke-width: 2px
33-
style B stroke: orange,fill: orange,color: black
34-
style C stroke-dasharray: 5 5
35-
linkStyle 0,3 stroke-width: 2px
36-
linkStyle 1,2 stroke-width: 1px
37-
```
20+
<Stream
21+
id="9103750883217fcb9274666fd57ebac1"
22+
title="Content compression"
23+
thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/Mermaid%20thumbnail_Content%20Compression.png"
24+
/>
3825

3926
:::note
4027
Customers can enable Zstandard compression through [Compression Rules](/rules/compression-rules/).

src/content/docs/ssl/concepts.mdx

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ description: This page defines and articulates key concepts that are relevant to
88
Cloudflare SSL/TLS and are used in the Cloudflare SSL/TLS documentation.
99
---
1010

11-
import { Render } from "~/components";
11+
import { Stream, Render } from "~/components";
1212

1313
This page defines and articulates key concepts that are relevant to Cloudflare SSL/TLS and are used in this documentation. For more concepts and broader descriptions, check out the [Cloudflare Learning Center](https://www.cloudflare.com/learning/ssl/what-is-ssl/).
1414

@@ -22,12 +22,11 @@ Since [Cloudflare's global network](https://www.cloudflare.com/network/) is at t
2222

2323
The [edge certificates](/ssl/edge-certificates/) are the ones that Cloudflare presents to clients visiting your website or application. You can manage edge certificates through the [Cloudflare Dashboard](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates).
2424

25-
```mermaid
26-
flowchart LR
27-
accTitle: Edge certificate and origin certificate
28-
accDescr: Diagram showing how edge certificates are positioned between Cloudflare and the browser whereas origin certificates sit between Cloudflare and the origin server.
29-
A[Browser] <--Edge certificate--> B((Cloudflare))<--Origin certificate--> C[(Origin server)]
30-
```
25+
<Stream
26+
id="fe9344af4ab476bf81f4447000f36db66"
27+
title="SSL/TLS concepts"
28+
thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/Mermaid%20thumbnail_Concepts.png"
29+
/>
3130

3231
### Origin certificate
3332

src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,16 +9,15 @@ head:
99
description: Cloudflare matches the browser request protocol when connecting to the origin. If the browser uses HTTP, Cloudflare connects to the origin via HTTP; if HTTPS, Cloudflare uses HTTPS without validating the origin’s certificate. This mode is common for origins that use self-signed or otherwise invalid certificates.
1010
---
1111

12-
import { Render, TabItem, Tabs } from "~/components";
12+
import { Stream, Render, TabItem, Tabs } from "~/components";
1313

1414
When you set your encryption mode to **Full**, Cloudflare allows HTTPS connections between your visitor and Cloudflare and makes connections to the origin using the scheme requested by the visitor. If your visitor uses `http`, then Cloudflare connects to the origin using plaintext HTTP and vice versa.
1515

16-
```mermaid
17-
flowchart LR
18-
accTitle: Full SSL/TLS Encryption
19-
accDescr: With an encryption mode of Full, your application encrypts traffic going to and coming from Cloudflare but does not validate your origin certificate.
20-
A[Browser] <--Encrypted--> B((Cloudflare))<--Encrypted--> C[(Origin server)]
21-
```
16+
<Stream
17+
id="5ad2c494e2def51ac5bad8ef8948b7d1"
18+
title="Configure Full encryption mode"
19+
thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/Mermaid%20thumbnail_Full.png"
20+
/>
2221

2322
## Use when
2423

src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ head:
99
description: Regardless of whether the browser-to-Cloudflare connection uses HTTP or HTTPS, Cloudflare always connects to the origin over HTTPS with certificate validation.
1010
---
1111

12-
import { Render, Tabs, TabItem } from "~/components";
12+
import { Stream, Render, Tabs, TabItem } from "~/components";
1313

1414
:::note
1515

@@ -20,12 +20,12 @@ When you set your encryption mode to **Strict (SSL-Only Origin Pull)**, connecti
2020

2121
The certificate presented by the origin will be validated the same as with [Full (strict) mode](/ssl/origin-configuration/ssl-modes/full-strict/).
2222

23-
```mermaid
24-
flowchart LR
25-
accTitle: Strict (SSL-Only Origin Pull) SSL/TLS Encryption
26-
accDescr: With an encryption mode of Strict (SSL-Only Origin Pull), all connections to the origin will always be made using SSL/TLS.
27-
A[Browser] <--Encrypted--> B((Cloudflare))<--Encrypted--> C[("Origin server (verified) #9989;")]
28-
```
23+
<Stream
24+
id="f407072cb5b4837c8c3a58a69cde90b5"
25+
title="Configure Strict encryption mode"
26+
thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/Mermaid%20thumbnail_Strict.png"
27+
/>
28+
2929

3030
## Use when
3131

src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx

Lines changed: 7 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ description: Learn how to troubleshoot ERR_SSL_VERSION_OR_CIPHER_MISMATCH when
1010
using Cloudflare SSL/TLS.
1111
---
1212

13-
import { Render } from "~/components";
13+
import { Stream, Render } from "~/components";
1414

1515
After you [add a new domain](/fundamentals/manage-domains/add-site/) to Cloudflare, your visitors' browsers might display one of the following errors:
1616

@@ -27,17 +27,12 @@ This error occurs when your domain or subdomain is not covered by an SSL/TLS cer
2727

2828
## Decision tree
2929

30-
```mermaid
31-
flowchart TD
32-
accTitle: Troubleshooting ERR_SSL_VERSION_OR_CIPHER_MISMATCH decision tree
33-
A>Is your certificate active?] -- Yes --> B>Is the DNS record proxied?]
34-
A -- No --> C[Wait for certificate to activate or pause Cloudflare]
35-
B -- No --> D[Proxy the DNS record]
36-
B -- Yes --> E>Are you using a custom certificate?]
37-
E -- Yes --> F[Custom certificate may be expired]
38-
E -- No --> G>Are you accessing a multi-level subdomain?]
39-
G -- Yes --> H[Get an advanced or custom certificate]
40-
```
30+
<Stream
31+
id="ff42f110f3781b88b02f36bcef96f7f8"
32+
title="Manage SSL version or cipher mismatch errors"
33+
thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/Mermaid%20thumbnail_Cipher.png"
34+
/>
35+
4136

4237
---
4338

0 commit comments

Comments
 (0)