002: improve blockquotes with figcaptions, minor edits
All checks were successful
ci/woodpecker/push/build-deploy Pipeline was successful

This commit is contained in:
41666 2025-05-16 18:14:31 -07:00
parent 8539c27cae
commit 84473fb544
2 changed files with 14 additions and 2 deletions

View file

@ -96,6 +96,18 @@
width: fit-content; width: fit-content;
} }
.doll-quote figcaption {
font-size: 0.8em;
color: var(--dark2);
background-color: var(--middle1);
width: fit-content;
padding: 0 0.5ch;
}
.doll-quote figcaption + blockquote {
border-top: 2px solid var(--middle1);
}
.mermaid { .mermaid {
width: fit-content; width: fit-content;
color: var(--middle1); color: var(--middle1);

View file

@ -119,7 +119,7 @@ description: how it stores secrets alongside its code
age answers that question by letting doll use ed25519 keys to encrypt and decrypt doll's data. age answers that question by letting doll use ed25519 keys to encrypt and decrypt doll's data.
[quote:ed25519 would be a good name for a doll... ^n] [quote(important ^noe message):ed25519 would be a good name for a doll!!]
since we're deploying to machines with presumably an SSH server running, and presumably since we're deploying to machines with presumably an SSH server running, and presumably
the doll also has an SSH client, all of these ends have SSH keys we can use the doll also has an SSH client, all of these ends have SSH keys we can use
@ -366,7 +366,7 @@ description: how it stores secrets alongside its code
&secrets........ but what about automation &secrets........ but what about automation
that silly [code:.sops.yaml] thing huh, c: that silly [code:.sops.yaml] third thing it mentioned huh? c:
why did we tag the age keys with [code:op_] and [code:m_]? so we can find them. in a script. why did we tag the age keys with [code:op_] and [code:m_]? so we can find them. in a script.