Better OL styling

This commit is contained in:
David Eisinger
2025-02-17 02:06:12 -05:00
parent a301186cfc
commit 685c307462
4 changed files with 15 additions and 23 deletions

View File

@@ -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 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 and 30 seconds, respectively, but you should use whatever makes you
feel good in your heart). 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` 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 9. Give your function permissions to read and write to/from the two
buckets. buckets.
10. And finally, the code. We'll manage that locally rather than using 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) walkthrough](https://docs.aws.amazon.com/lambda/latest/dg/ruby-package.html)
of how to do it but I'll summarize: of how to do it but I'll summarize:
1. <span>Install your gems locally with `bundle install --path vendor/bundle`.</span> 1. Install your gems locally with `bundle install --path vendor/bundle`.
2. <span>Edit your code (in our case, it lives in `lambda_function.rb`).</span> 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 3. Make a simple shell script that zips up your function and gems and
sends it up to AWS: sends it up to AWS:

View File

@@ -35,7 +35,7 @@ purposes, most of these principles don't apply. Our typical setup
involves the following containers, orchestrated with Docker Compose: involves the following containers, orchestrated with Docker Compose:
1. The application (e.g. Rails, Django, or Phoenix) 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) 3. A database (typically PostgreSQL)
4. Additional necessary infrastructure (e.g. Redis, ElasticSearch, 4. Additional necessary infrastructure (e.g. Redis, ElasticSearch,
Mailhog) Mailhog)

View File

@@ -57,28 +57,21 @@ ol {
margin: 0; margin: 0;
padding: 0; padding: 0;
counter-reset: item; counter-reset: item;
display: grid;
grid-template-columns: auto 1fr;
gap: 1ch;
li { li {
list-style: none; counter-increment: item;
display: contents; display: table;
overflow-wrap: anywhere; table-layout: fixed;
width: 100%;
p {
margin: 0;
}
} }
li::before { li::before {
content: counter(item) '.'; content: counter(item) ".";
counter-increment: item; display: table-cell;
} padding-right: 1ch;
white-space: nowrap;
ol { width: 3ch;
gap: 0 1ch;
grid-column: 2;
} }
} }

View File

@@ -47,7 +47,6 @@
{{- /* Misc. markup fixes */ -}} {{- /* Misc. markup fixes */ -}}
{{- $content = $content | replaceRE `<!--more-->\n+` "" -}} {{- $content = $content | replaceRE `<!--more-->\n+` "" -}}
{{- $content = $content | replaceRE `<[/]?span>` "" -}}
{{- $content = $content | replaceRE `(?m)^ >` ">" -}} {{- $content = $content | replaceRE `(?m)^ >` ">" -}}
{{- $content = $content | replaceRE `(?m)^ \*` "* ⇢" -}} {{- $content = $content | replaceRE `(?m)^ \*` "* ⇢" -}}
{{- $content = $content | replaceRE `(?m)^- ` "* " -}} {{- $content = $content | replaceRE `(?m)^- ` "* " -}}