commit 685c3074626d052e837fd2e40fe48843402dcc48
parent a301186cfc7b617ea7668dbbf7ddd9b7ab0f1d0c
Author: David Eisinger <[email protected]>
Date: Mon, 17 Feb 2025 02:06:12 -0500
Better OL styling
Diffstat:
4 files changed, 15 insertions(+), 23 deletions(-)
diff --git a/content/elsewhere/email-photos-to-an-s3-bucket-with-aws-lambda-with-cropping-in-ruby/index.md b/content/elsewhere/email-photos-to-an-s3-bucket-with-aws-lambda-with-cropping-in-ruby/index.md
@@ -74,9 +74,9 @@ It's a lot, to be sure, but it comes together pretty easily:
ImageMagick as a layer[^1] and bump the memory and timeout (I used 512 MB
and 30 seconds, respectively, but you should use whatever makes you
feel good in your heart).
-8. <span>Create a couple environment variables: `BUCKET` should be name of
+8. Create a couple environment variables: `BUCKET` should be name of
the S3 bucket you want to upload photos to, and `AUTHORIZED_EMAILS`
- to hold all the valid email addresses separated by semicolons.</span>
+ to hold all the valid email addresses separated by semicolons.
9. Give your function permissions to read and write to/from the two
buckets.
10. And finally, the code. We'll manage that locally rather than using
@@ -187,8 +187,8 @@ CLI](https://aws.amazon.com/cli/). [Here's a pretty good
walkthrough](https://docs.aws.amazon.com/lambda/latest/dg/ruby-package.html)
of how to do it but I'll summarize:
-1. <span>Install your gems locally with `bundle install --path vendor/bundle`.</span>
-2. <span>Edit your code (in our case, it lives in `lambda_function.rb`).</span>
+1. Install your gems locally with `bundle install --path vendor/bundle`.
+2. Edit your code (in our case, it lives in `lambda_function.rb`).
3. Make a simple shell script that zips up your function and gems and
sends it up to AWS:
diff --git a/content/elsewhere/local-docker-best-practices/index.md b/content/elsewhere/local-docker-best-practices/index.md
@@ -35,7 +35,7 @@ purposes, most of these principles don't apply. Our typical setup
involves the following containers, orchestrated with Docker Compose:
1. The application (e.g. Rails, Django, or Phoenix)
-2. <span>A JavaScript watcher/compiler (e.g. `webpack-dev-server`)</span>
+2. A JavaScript watcher/compiler (e.g. `webpack-dev-server`)
3. A database (typically PostgreSQL)
4. Additional necessary infrastructure (e.g. Redis, ElasticSearch,
Mailhog)
diff --git a/themes/v2/assets/css/style.scss b/themes/v2/assets/css/style.scss
@@ -57,28 +57,21 @@ ol {
margin: 0;
padding: 0;
counter-reset: item;
- display: grid;
- grid-template-columns: auto 1fr;
- gap: 1ch;
- li {
- list-style: none;
- display: contents;
- overflow-wrap: anywhere;
-
- p {
- margin: 0;
- }
- }
- li::before {
- content: counter(item) '.';
+ li {
counter-increment: item;
+ display: table;
+ table-layout: fixed;
+ width: 100%;
}
- ol {
- gap: 0 1ch;
- grid-column: 2;
+ li::before {
+ content: counter(item) ".";
+ display: table-cell;
+ padding-right: 1ch;
+ white-space: nowrap;
+ width: 3ch;
}
}
diff --git a/themes/v2/layouts/partials/gemtext.gmi b/themes/v2/layouts/partials/gemtext.gmi
@@ -47,7 +47,6 @@
{{- /* Misc. markup fixes */ -}}
{{- $content = $content | replaceRE `<!--more-->\n+` "" -}}
-{{- $content = $content | replaceRE `<[/]?span>` "" -}}
{{- $content = $content | replaceRE `(?m)^ >` ">" -}}
{{- $content = $content | replaceRE `(?m)^ \*` "* ⇢" -}}
{{- $content = $content | replaceRE `(?m)^- ` "* " -}}
