fix: padding

infra/README.md

@@ -255,6 +255,41 @@ The Forgejo Actions workflow (`.forgejo/workflows/deploy.yml`) triggers on push
 
 ---
 
+## Countdown Static Site (Caddy)
+
+`deploy-countdown.yml` provisions a **fresh standalone VPS** that serves only the
+static `countdown.html` (repo root). It installs Caddy, uploads the page, and lets
+Caddy obtain + auto-renew the TLS certificate for `hl-mutter-teresa-chemnitz.de`
+and `www.hl-mutter-teresa-chemnitz.de`.
+
+```bash
+cd infra/ansible
+
+# 1. Point the inventory at the VPS and confirm the domains
+#    edit inventory/countdown/hosts.yml -> ansible_host, countdown_domain, countdown_aliases
+
+# 2. Make sure DNS A/AAAA records for both names point at the VPS first
+#    (Caddy's ACME challenge needs them resolving), then run with the root
+#    password (--ask-pass needs `sshpass` installed locally):
+ansible-playbook playbooks/deploy-countdown.yml -i inventory/countdown/hosts.yml --ask-pass
+```
+
+> Authenticating with the root password? Install `sshpass` first
+> (`brew install hudochenkov/sshpass/sshpass` on macOS, `apt install sshpass` on
+> Debian/Ubuntu). Once you've added an SSH key to the box you can drop
+> `--ask-pass` and set `ansible_ssh_private_key_file` in the inventory instead.
+
+**What it does:**
+
+1. Installs Caddy + ufw (allows 22/80/443)
+2. Uploads `countdown.html` to `/var/www/countdown/index.html`
+3. Deploys a Caddyfile serving both domains; Caddy handles HTTPS automatically
+
+**Re-running** is the normal way to publish content changes — it re-uploads the
+HTML and reloads Caddy. The certificate is managed entirely by Caddy.
+
+---
+
 ## Production Setup
 
 1. Copy and edit the production inventory:

src/pageComponents/Parish/Parish.tsx

@@ -67,7 +67,7 @@ export const Parish = (
         link={<CalendarAnnouncementButtons calendar={calendar} announcements={announcement}/>}
       />
 
-      <Section>
+      <Section padding={"small"} paddingBottom={"large"}>
         <Container>
           <Row>
             <Col>