The dominant model for publishing knowledge online has not changed much since the early 2000s: write something, polish it, publish it, move on. Blog posts are finished when they are published.
That model creates a hidden cost. The knowledge that does not make it into a finished piece — the half-formed ideas, the developing hypotheses, the notes that are useful but not polished — stays private. Publicly, you appear to know only what you have been willing to finalize and ship.
Digital gardens are a different publishing philosophy. Instead of treating knowledge as a series of finished articles, a garden treats it as an evolving network of ideas at different stages of development. Some notes are rough seedlings. Some are well-developed and stable. All of them are public, linked, and growing.
The term gained momentum through writers like Maggie Appleton, who documented the history and practice of digital gardening, and Andy Matuschak, whose public evergreen notes embody the philosophy. For engineers who write technically, it offers an alternative to the pressure of the polished post.
The Garden Metaphor
