general · 1 min read · Kartavya

Building the Garden

Boundaries for a digital garden that can grow without becoming a framework maze.

digital-garden architecture

Properties
status
published
aliases
['garden architecture']
tags
['digital-garden', 'architecture']
More properties
title: Building the Garden
date: 2026-07-22
description: Boundaries for a digital garden that can grow without becoming a framework maze.
excerpt: Boundaries for a digital garden that can grow without becoming a framework maze.
outgoing_links: ['a-room-for-reading']
source_dir: /home/runner/work/The-Bard/The-Bard/frontend/content
source_mode: markdown
has_math: False
has_mermaid: False
site_namespace: bard
freshness: 0.9999985169885733
entropy_decay: 1.48301142666174e-06
modified_at: 2026-07-22T20:19:38+00:00
source_revision: c1f565fb80dcaad1d50a7691802b99cd2af97fed
version: c1f565fb80dc
link_diagnostics: {'missing': [], 'ambiguous': []}

A digital garden needs structure, but structure should not erase the odd corners that make a personal website personal.

One contract, many editions

Every article can expose a small common record: identity, dates, aliases, tags, and links. The ordinary edition uses the shared reading shell. A bespoke edition may instead be a complete HTML document with its own styles and scripts.

Isolation is a feature

Shared articles receive layered, scoped CSS. Bespoke documents live at separate paths. Neither side needs to win a specificity war, and the site can stay coherent without making every page uniform.

Grow in visible phases

  • First, make reading excellent.
  • Then make links and backlinks deterministic.
  • Add graph views only after the underlying index is trustworthy.
  • Treat a dashboard as an optional authoring client, never a runtime dependency.

The garden is static when published. Tools may help prepare it later, but a visitor receives durable HTML, CSS, and JavaScript that need no application server.

Connected Chronicles