Articles
Longer pieces on how something works and why I set it up the way I did.
-
Astro Justified Gallery Layout
My npm package @altner/astro-justified-gallery-layout: a small justified gallery for Astro with EXIF, LQIP previews, a virtual variant and a lightbox.
-
Astro Client Islands under a Strict CSP
Why Astro islands fail silently under script-src 'self', how I allowed the two hydration inlines by sha256 hash, and a deploy check for hash drift.
-
A GDPR-Compliant Google Maps Embed
An Astro component that loads Google Maps only after consent, stores the decision in localStorage and builds Google and Apple Maps links from coordinates.
-
A Callout Component for Astro
A reusable Astro info box with info, note and warning variants, an optional title, social links and a members section with links per person.
-
Why Stadia Maps Instead of OpenStreetMap Tiles
For the photo world map I wanted OpenStreetMap data from an EU server without running a tile server myself. Stadia Maps met every criterion.
-
Leaflet and Stadia Maps Behind a Strict CSP
Two fixes that made the photo world map work in production: the tile host in img-src and a Referrer-Policy of origin on the tiles.
-
A GDPR-Compliant YouTube Embed
An Astro component that loads YouTube only after a click: show once, agree and remember, or just the link. No cookie, no request to Google before consent.
-
Setting Up a Forgejo Actions Runner
Push-to-deploy with a self-hosted Forgejo Actions runner on the same VPS: own user, no Docker, narrow sudo rights and secrets kept in Forgejo.
-
Security Headers in Caddy
A strict Content Security Policy, HSTS and no-referrer in a Caddy site block, checked with Webbkoll, securityheaders.com and the Mozilla Observatory.