few small tweaks

README.md

@@ -1,94 +1 @@
 # Siblinghood of the Traveling Greeting Card
-
-## full drone/submodule setup from scratch
-
-### 1. create repo
-
-in heckin gitea, create destination repo.
-
-### 2. add dronefile to source repo
-
-Filename: `.drone.yml`, in root of repo. Note the `<vars>` to replace.
-
-```yaml
-kind: pipeline
-type: docker
-name: default
-
-steps:
-  - name: build
-    image: node:current
-    environment:
-      REPOSITORY: <dest-repo>
-      GIT_USER: <username>
-      GIT_TOKEN:
-        from_secret: GIT_TOKEN
-    commands:
-      - git config credential.helper '!f() { echo username=$GIT_USER; echo "password=$GIT_TOKEN"; };f'
-      - git submodule update --remote --init --merge
-      - npm install
-      - npm run build
-      - apt-get update && apt-get install -y rsync
-      - rsync -uavh _site/ $REPOSITORY --delete --exclude .git
-      - cd $REPOSITORY
-      - git checkout main
-      - git config --global --add safe.directory /drone/src/$REPOSITORY
-      - git add -A
-      - git commit -m "drone build $(TZ=':America/Los_Angeles' date)"
-      - git push
-```
-
-### 3. create PAT (one-time, not per repo)
-
-in heckin, go to settings > applications, and create a PAT with read & write permissions to repositories.
-
-### 4. activate project in drone and add PAT
-
-in drone, find your project and activate it.
-
-in the settings, I chose to disable pull requests and forks. I set my runner timeout to 15m.
-
-you can set your PAT either as a project secret or an organization secret. In either case call it `GIT_TOKEN`.
-
-### 5. first commit to submodule
-
-assuming we are committing the _site folder...
-
-```sh
-cp -r _site ../temp
-cd ../temp
-
-git init
-git add -A
-git commit -m "first"
-
-git remote add origin <remote-url>
-git push -u origin main
-```
-
-### 6. add submodule to local repo
-
-in root dir of local repo, add the submodule.
-
-```sh
-git submodule add <remote-url>
-```
-
-if you used the SSH url, set it to the HTTPS url.
-
-```sh
-git submodule set-url <dest-repo> <remote-url-https>
-git add .gitmodules # the changes from submodule add are auto-staged, this config change isn't
-```
-
-commit your changes and push.
-
-```sh
-git commit -m "add submodule"
-```
-
-(commit your dronefile changes too.)
-
-### 7. profit
-
-if it doesn't work, cry

css/main.css

@@ -76,7 +76,7 @@ p {
 
 @media (max-width: 650px) {
 	p {
-		font-size: .9rem;
+		font-size: .95rem;
 		line-height: 1.3rem;
 	}
 }
@@ -149,7 +149,7 @@ ul {
 
 @media (max-width: 650px) {
 	ul {
-		font-size: .9rem;
+		font-size: .95rem;
 		line-height: 1.3rem;
 	}
 }

src/card-one.njk

@@ -7,7 +7,8 @@ eleventyNavigation:
 
 <h1>The Travels of <span class="card">Card One</span></h1>
 
-<p><span class="card">Card one</span> has 16 total recipients. Its journey began in late December, 2025.</p>
+<p><span class="card">Card one</span> has 16 total recipients. Its journey began in
+<time datetime="2025-12-27">late December, 2025</time>.</p>
 
 {% set stops = collections["1a"] %}
 {% include "card.njk" %}

src/card-three.njk

@@ -7,7 +7,8 @@ eleventyNavigation:
 
 <h1>The Travels of <span class="card">Card Three</span></h1>
 
-<p><span class="card">Card three</span> has 16 total recipients. Its journey began in late July, 2026.</p>
+<p><span class="card">Card three</span> has 16 total recipients. Its journey began in
+<time datetime="2026-07-20">late July, 2026</time>.</p>
 
 {% set stops = collections["3"] %}
 {% include "card.njk" %}

src/card-two.njk

@@ -7,7 +7,8 @@ eleventyNavigation:
 
 <h1>The Travels of <span class="card">Card Two</span></h1>
 
-<p><span class="card">Card two</span> has 16 total recipients. Its journey began in early January, 2026.</p>
+<p><span class="card">Card two</span> has 16 total recipients. Its journey began in
+<time datetime="2026-01-06">early January, 2026</time>.</p>
 
 {% set stops = collections["2"] %}
 {% include "card.njk" %}

src/index.md

@@ -87,7 +87,7 @@ I'll be doing my level best to track the card's movement, so as it is sent aroun
 
 ## I want in!
 
-as stated above, signups for the rounds beginning <time datetime="2026-01-01">January 1st, 2026</time> and <time datetime="2026-06-04">June 4th, 2026</time> are closed. However, you may still sign up in case of future rounds.
+as stated above, signups for the rounds beginning <time datetime="2026-01-01">January 1st, 2026</time> and <time datetime="2026-06-04">June 4th, 2026</time> are **closed**. However, you may still sign up in case of future rounds.
 
 [sign up for the siblinghood of the traveling greeting card](https://airtable.com/appdoHZsRDUzgYu9q/pagsr9LVAqKx29gDl/form).