On a static website every page is built in advance, and the web server only serves files. That makes it fast, hard to attack and cheap to host for a long time. Anything that differs per visitor, such as logins, comments or search over very large collections, needs extra services or JavaScript in the browser. The counterpart is a dynamic website, which assembles each page from a database on every request.
- Covered in
-
- 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.
- 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 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.
- Adding Notes, Links and Archives Three sections of my old Astro site: short notes rendered inline, a link log as a data collection, and one archive across every content type.
- 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.
- 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.
- Building the Photo Stream The photo stream of my old Astro site: JSON sidecars next to each JPG, import.meta.glob, a justified grid and batches revealed on scroll.
- Collection Sets and Category Collections One boolean in the frontmatter told the photo sets of my old site apart from pure navigation nodes, so only finished sets reached the archive.
- Markdown as a Database For a personal website, a folder of Markdown files with a structured header replaces the database, as long as a schema checks it.
- My Old Astro Website My old site at adrian-altner.de: Astro with the Node adapter, typed content collections, IndieWeb features and photos as files with JSON sidecars.
- Obfuscating Contact Data on a Static Site Base64 in a data attribute and reversed text flipped back by CSS keep the imprint's email address away from harvesters and from copy and paste.
- Obsidian Wiki-Links in Astro with a Remark Plugin A small Remark plugin that turns Obsidian [[wiki-links]] into normal links at build time, with labels, heading anchors and a fallback for unknown targets.
- Photo Albums with Astro's Content Layer Album pages on top of the photo stream of my old site: a content collection per album, covers by filename, album-scoped photo routes and a sub-nav.
- Replacing justified-layout with My Own Package How my old site swapped Flickr's unmaintained justified-layout for computeLayout() from my own package, without touching the photo tree.
- RSS News with n8n and OpenRouter Guide: n8n reads security notices, a language model rates and rewrites them, and a restricted SSH script commits them to the Git repository of a static site.
- Structuring Photos as a Collection Tree How the photos of my old Astro site grew from flat albums into a recursive tree: one catch-all route, photos per node, breadcrumbs and tag pages.
- Why the Photo Tree Is No Content Collection Anymore When my old Astro site went bilingual, the photo tree left the content layer: every photo and node needs both languages in one file.
- Mentioned in
-
- How an LLM Wiki Works How an LLM wiki works, shown on this knowledge base: Markdown in its own Git repository, a Python tool with MCP for agents, and a website that only displays it.
- See also
-
- Search Engine Optimization Measures that help search engines find, understand and properly display pages. The basis is stable URLs, clear titles and internal links.
- Tags