2.0 The Slow Web & IndieWeb Manifesto
Standard Garden is born from a quiet refusal. In an era dominated by algorithmic feeds, manufactured urgency, and walled corporate platforms designed to extract human attention, we choose a different path: the Slow Web.
We believe the web is at its best when it is quiet, durable, and deliberate. Here, words and ideas are not tossed into an ephemeral river to drown under tomorrow’s notifications. They are planted in fertile soil, tended with care, and allowed to grow over seasons and years.
The Lineage: The IndieWeb & Digital Gardens
Standard Garden is not an isolated experiment. It stands proudly on the shoulders of decentralization and thoughtful web architecture:
1. The IndieWeb Movement (indieweb.org)
The IndieWeb is a people-focused alternative to the corporate web. Its principles form our bedrock:
- Own Your Identity & Data: Your online presence should never belong to a landlord. Instead of renting an
@handleon a platform that can censor, alter, or monetize your words at will, your digital home belongs on your own domain. - POSSE (Publish on Own Site, Syndicate Elsewhere): Your writing lives first and foremost in your personal sanctuary. If you choose to share reflections with external networks, you do so as a broadcast from your sovereign home, never as a locked asset inside a proprietary silo.
- Decentralized Backlinks & Webmentions: Meaningful communication doesn’t need a monopolistic intermediary. When an author cites another garden, protocols like W3C Webmentions and semantic backlinks build an open web of dialogue between independent thinkers.
2. The Digital Garden vs. The Stream
Popularized by thinkers like Mike Caulfield (The Garden and the Stream), Maggie Appleton, and Tom Critchlow, the digital garden inverts the tyranny of chronological feeds:
- The Stream: Information flows past like an accelerating torrent. Yesterday’s essay is deemed obsolete; last month’s reflection is dead. The stream demands constant posting, values novelty over substance, and thrives on dopamine loops.
- The Garden: Space replaces time. Notes are living plants arranged by topography and relation rather than publication date. A note written five years ago is not stale—it is a perennial that has accrued backlinks, accumulated context, and deepened its roots. In a garden, we think in public and embrace ideas that evolve.
Two Distinct Realms: The Garden vs. The Framework
To understand this project is to recognize its two foundational layers:
- 🌱 Standard Garden (
standard.garden/stnd.gd): The author’s sanctuary. This is the publication layer, the typographic interface, and the direct bridge to your local Obsidian vault. It is where writers, photographers, and essayists cultivate their work without ever thinking about servers, configuration files, or cloud infrastructure. - ⚙️ The Standard Framework (
stnd.build): The modular architectural engine beneath. Built on Astro, Cloudflare edge computing, and strict CSS typography tokens, it is the technical foundation that powers the garden. As an author, you never need to touch its gears to enjoy its shade.
The Four Invariants
Every feature, interface detail, and line of code in Standard Garden must pass through four non-negotiable filters:
- Beauty is Default: Five centuries of classical typography—Gutenberg’s baseline grid, Aldus Manutius’s proportions, Swiss modernist precision—are applied automatically. Your thoughts deserve visual dignity.
- Friction is the Enemy: Ten seconds from thought to a beautiful, permanent URL. No required signups, no heavy dashboards, no deployment delays.
- File over App: You own your files. Plain local Markdown is sovereign; the web application is merely an enlightened mirror of your local workshop.
- Ecologically Honest: Efficient edge execution, static HTML delivery, and zero wasted server cycles. Our architecture is designed to respect the physical resources of the earth.
See Also
- The Three Respects Charter — author, reader, and world
- The Six Classical Temperaments — the typographic DNA of the garden
- The Obsidian Protocol — connecting your local vault to the web