CSS tweak on search results; Disabled copy button on text and json co…

…deblocks

Signed-off-by: Travis Beckham <[email protected]>

CONTRIBUTING.md

@@ -53,7 +53,7 @@ message.
 
 Finalized commit messages should be in the following format:
 
-```text
+```text {class=disable-copy}
 Subject
 
 Problem
@@ -74,12 +74,12 @@ Fixes #[Github issue ID]
 
 ##### Examples #####
 
-```text
+```text {class=disable-copy}
 bad: server disconnects should cause dst client disconnects.
 good: Propagate disconnects from source to destination
 ```
 
-```text
+```text {class=disable-copy}
 bad: support tls servers
 good: Introduce support for server-side TLS (#347)
 ```

linkerd.io/README.md

@@ -37,7 +37,7 @@ have to specify them in the frontmatter. You can simply name them `cover`,
 `thumbnail` or `feature`, place them in the blog post folder, and they will
 automattically be used. For example:
 
-```text
+```text {class=disable-copy}
 blog/
 └── 2024/
     └── 0102-my-blog-post

linkerd.io/assets/scss/app/_search.scss

@@ -17,7 +17,7 @@
 
   // Add extra space between header and entries
   & > :nth-child(2) {
-    margin-top: spacer(7); // Override stack
+    margin-top: spacer(6); // Override stack
   }
 }
 

linkerd.io/content/2-edge/features/access-logging.md

@@ -33,7 +33,7 @@ Setting the `config.linkerd.io/access-log: "apache"` annotation configures the
 proxy to emit HTTP access logs in the [Apache Common Log
 Format](https://en.wikipedia.org/wiki/Common_Log_Format). For example:
 
-```text
+```text {class=disable-copy}
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.071809491Z] "GET http://webapp:7000/ HTTP/2.0" 200
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.187706137Z] "POST http://webapp:7000/authors HTTP/2.0" 303
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.301798187Z] "GET http://webapp:7000/authors/104 HTTP/2.0" 200
@@ -44,7 +44,7 @@ Format](https://en.wikipedia.org/wiki/Common_Log_Format). For example:
 Setting the `config.linkerd.io/access-log: json` annotation configures the proxy
 to emit access logs in a JSON format. For example:
 
-```json
+```json {class=disable-copy}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"GET","processing_ns":"39826","request_bytes":"","response_bytes":"19627","status":200,"timestamp":"2022-08-23T20:33:42.321746212Z","total_ns":"14441135","trace_id":"","uri":"http://webapp:7000/","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"POST","processing_ns":"30036","request_bytes":"33","response_bytes":"0","status":303,"timestamp":"2022-08-23T20:33:42.436964052Z","total_ns":"14122403","trace_id":"","uri":"http://webapp:7000/authors","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"GET","processing_ns":"38664","request_bytes":"","response_bytes":"2350","status":200,"timestamp":"2022-08-23T20:33:42.551768300Z","total_ns":"6998222","trace_id":"","uri":"http://webapp:7000/authors/105","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}

linkerd.io/content/2-edge/tasks/books.md

@@ -212,7 +212,7 @@ kubectl -n booksapp get httproutes.gateway.networking.k8s.io \
 
 Notice that the `Accepted` and `ResolvedRefs` conditions are `True`.
 
-```json
+```json {class=disable-copy}
 {
   "lastTransitionTime": "2024-08-03T01:38:25Z",
   "message": "",

linkerd.io/content/2-edge/tasks/manually-rotating-control-plane-tls-credentials.md

@@ -36,7 +36,7 @@ linkerd check --proxy
 If your configuration is valid and your credentials are not expiring soon, you
 should see output similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -64,7 +64,7 @@ valid, continue on with this document.)
 For example, if your issuer certificate has expired, you will see a message
 similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -79,7 +79,7 @@ see https://linkerd.io/2/checks/#l5d-identity-issuer-cert-is-time-valid for hint
 
 If your trust anchor has expired, you will see a message similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -172,7 +172,7 @@ linkerd check --proxy
 You might have to wait a few moments until all the pods have been restarted and
 are configured with the correct trust anchor. Meanwhile you might observe warnings:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -204,7 +204,7 @@ When the rollout completes, your `check` command should stop warning you that
 pods need to be restarted. It may still warn you, however, that your issuer
 certificate is about to expire soon:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -286,7 +286,7 @@ linkerd check --proxy
 You should see output without any certificate expiration warnings (unless an
 expired trust anchor still needs to be removed):
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -332,7 +332,7 @@ linkerd check --proxy
 And, again, the output of the `check` command should not produce any warnings or
 errors:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid

linkerd.io/content/2-edge/tasks/multicluster.md

@@ -288,7 +288,7 @@ With the podinfo landing page available at
 `west` cluster right now. Alternatively, running `curl http://localhost:8080`
 will return a JSON response that looks something like:
 
-```json
+```json {class=disable-copy}
 {
   "hostname": "podinfo-5c8cf55777-zbfls",
   "version": "4.0.2",

linkerd.io/content/2.10/tasks/manually-rotating-control-plane-tls-credentials.md

@@ -35,7 +35,7 @@ linkerd check --proxy
 If your configuration is valid and your credentials are not expiring soon, you
 should see output similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -63,7 +63,7 @@ Certificates Guide](../replacing_expired_certificates/) instead.
 For example, if your issuer certificate has expired, you will see a message
 similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -78,7 +78,7 @@ see https://linkerd.io/2/checks/#l5d-identity-issuer-cert-is-time-valid for hint
 
 If your trust anchor has expired, you will see a message similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -161,7 +161,7 @@ linkerd check --proxy
 You might have to wait a few moments until all the pods have been restarted and
 are configured with the correct trust anchor. Meanwhile you might observe warnings:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -193,7 +193,7 @@ When the rollout completes, your `check` command should stop warning you that
 pods need to be restarted. It may still warn you, however, that your issuer
 certificate is about to expire soon:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -270,7 +270,7 @@ linkerd check --proxy
 You should see output without any certificate expiration warnings (unless an
 expired trust anchor still needs to be removed):
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -314,7 +314,7 @@ linkerd check --proxy
 Finally the output of the `check` command should not produce any warnings or
 errors:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid

linkerd.io/content/2.10/tasks/multicluster.md

@@ -285,7 +285,7 @@ With the podinfo landing page available at
 `west` cluster right now. Alternatively, running `curl http://localhost:8080`
 will return a JSON response that looks something like:
 
-```json
+```json {class=disable-copy}
 {
   "hostname": "podinfo-5c8cf55777-zbfls",
   "version": "4.0.2",

linkerd.io/content/2.11/tasks/manually-rotating-control-plane-tls-credentials.md

@@ -36,7 +36,7 @@ linkerd check --proxy
 If your configuration is valid and your credentials are not expiring soon, you
 should see output similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -64,7 +64,7 @@ valid, continue on with this document.)
 For example, if your issuer certificate has expired, you will see a message
 similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -79,7 +79,7 @@ see https://linkerd.io/2/checks/#l5d-identity-issuer-cert-is-time-valid for hint
 
 If your trust anchor has expired, you will see a message similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -178,7 +178,7 @@ linkerd check --proxy
 You might have to wait a few moments until all the pods have been restarted and
 are configured with the correct trust anchor. Meanwhile you might observe warnings:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -210,7 +210,7 @@ When the rollout completes, your `check` command should stop warning you that
 pods need to be restarted. It may still warn you, however, that your issuer
 certificate is about to expire soon:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -302,7 +302,7 @@ linkerd check --proxy
 You should see output without any certificate expiration warnings (unless an
 expired trust anchor still needs to be removed):
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -354,7 +354,7 @@ linkerd check --proxy
 And, again, the output of the `check` command should not produce any warnings or
 errors:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid

linkerd.io/content/2.11/tasks/multicluster.md

@@ -281,7 +281,7 @@ With the podinfo landing page available at
 `west` cluster right now. Alternatively, running `curl http://localhost:8080`
 will return a JSON response that looks something like:
 
-```json
+```json {class=disable-copy}
 {
   "hostname": "podinfo-5c8cf55777-zbfls",
   "version": "4.0.2",

linkerd.io/content/2.12/features/access-logging.md

@@ -33,7 +33,7 @@ Setting the `config.linkerd.io/access-log: "apache"` annotation configures the
 proxy to emit HTTP access logs in the [Apache Common Log
 Format](https://en.wikipedia.org/wiki/Common_Log_Format). For example:
 
-```text
+```text {class=disable-copy}
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.071809491Z] "GET http://webapp:7000/ HTTP/2.0" 200
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.187706137Z] "POST http://webapp:7000/authors HTTP/2.0" 303
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.301798187Z] "GET http://webapp:7000/authors/104 HTTP/2.0" 200
@@ -44,7 +44,7 @@ Format](https://en.wikipedia.org/wiki/Common_Log_Format). For example:
 Setting the `config.linkerd.io/access-log: json` annotation configures the proxy
 to emit access logs in a JSON format. For example:
 
-```json
+```json {class=disable-copy}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"GET","processing_ns":"39826","request_bytes":"","response_bytes":"19627","status":200,"timestamp":"2022-08-23T20:33:42.321746212Z","total_ns":"14441135","trace_id":"","uri":"http://webapp:7000/","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"POST","processing_ns":"30036","request_bytes":"33","response_bytes":"0","status":303,"timestamp":"2022-08-23T20:33:42.436964052Z","total_ns":"14122403","trace_id":"","uri":"http://webapp:7000/authors","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"GET","processing_ns":"38664","request_bytes":"","response_bytes":"2350","status":200,"timestamp":"2022-08-23T20:33:42.551768300Z","total_ns":"6998222","trace_id":"","uri":"http://webapp:7000/authors/105","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}

linkerd.io/content/2.12/tasks/manually-rotating-control-plane-tls-credentials.md

@@ -36,7 +36,7 @@ linkerd check --proxy
 If your configuration is valid and your credentials are not expiring soon, you
 should see output similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -64,7 +64,7 @@ valid, continue on with this document.)
 For example, if your issuer certificate has expired, you will see a message
 similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -79,7 +79,7 @@ see https://linkerd.io/2/checks/#l5d-identity-issuer-cert-is-time-valid for hint
 
 If your trust anchor has expired, you will see a message similar to:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -172,7 +172,7 @@ linkerd check --proxy
 You might have to wait a few moments until all the pods have been restarted and
 are configured with the correct trust anchor. Meanwhile you might observe warnings:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -204,7 +204,7 @@ When the rollout completes, your `check` command should stop warning you that
 pods need to be restarted. It may still warn you, however, that your issuer
 certificate is about to expire soon:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -286,7 +286,7 @@ linkerd check --proxy
 You should see output without any certificate expiration warnings (unless an
 expired trust anchor still needs to be removed):
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid
@@ -332,7 +332,7 @@ linkerd check --proxy
 And, again, the output of the `check` command should not produce any warnings or
 errors:
 
-```text
+```text {class=disable-copy}
 linkerd-identity
 ----------------
 √ certificate config is valid

linkerd.io/content/2.12/tasks/multicluster.md

@@ -288,7 +288,7 @@ With the podinfo landing page available at
 `west` cluster right now. Alternatively, running `curl http://localhost:8080`
 will return a JSON response that looks something like:
 
-```json
+```json {class=disable-copy}
 {
   "hostname": "podinfo-5c8cf55777-zbfls",
   "version": "4.0.2",

linkerd.io/content/2.13/features/access-logging.md

@@ -33,7 +33,7 @@ Setting the `config.linkerd.io/access-log: "apache"` annotation configures the
 proxy to emit HTTP access logs in the [Apache Common Log
 Format](https://en.wikipedia.org/wiki/Common_Log_Format). For example:
 
-```text
+```text {class=disable-copy}
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.071809491Z] "GET http://webapp:7000/ HTTP/2.0" 200
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.187706137Z] "POST http://webapp:7000/authors HTTP/2.0" 303
 10.42.0.63:51160 traffic.booksapp.serviceaccount.identity.linkerd.cluster.local - [2022-08-23T20:28:20.301798187Z] "GET http://webapp:7000/authors/104 HTTP/2.0" 200
@@ -44,7 +44,7 @@ Format](https://en.wikipedia.org/wiki/Common_Log_Format). For example:
 Setting the `config.linkerd.io/access-log: json` annotation configures the proxy
 to emit access logs in a JSON format. For example:
 
-```json
+```json {class=disable-copy}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"GET","processing_ns":"39826","request_bytes":"","response_bytes":"19627","status":200,"timestamp":"2022-08-23T20:33:42.321746212Z","total_ns":"14441135","trace_id":"","uri":"http://webapp:7000/","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"POST","processing_ns":"30036","request_bytes":"33","response_bytes":"0","status":303,"timestamp":"2022-08-23T20:33:42.436964052Z","total_ns":"14122403","trace_id":"","uri":"http://webapp:7000/authors","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}
 {"client.addr":"10.42.0.70:32996","client.id":"traffic.booksapp.serviceaccount.identity.linkerd.cluster.local","host":"webapp:7000","method":"GET","processing_ns":"38664","request_bytes":"","response_bytes":"2350","status":200,"timestamp":"2022-08-23T20:33:42.551768300Z","total_ns":"6998222","trace_id":"","uri":"http://webapp:7000/authors/105","user_agent":"Go-http-client/1.1","version":"HTTP/2.0"}