A landscape design is a system with an unusual property: its components grow, die, spread, and shade each other. Most documentation treats it as a static drawing, which is why the as-built and the as-maintained diverge within three seasons. Shapezo, the content-shaping discipline for engineering-grade knowledge, models the landscape the way a platform models a living service: typed entities, declared invariants, per-audience renderers, and a registered asset pipeline. This article walks the model end to end.
The entity model
Five entity types carry the whole domain. Each has a stable identifier, a lifecycle state, and required fields.
The Space is the experiential unit: a terrace, lawn panel, courtyard, meadow, or border. Each space carries an intent sentence, a sun and wind exposure profile, and a target experience. Spaces tile a site and may nest, as a border nests inside a lawn room.
The Planting is the biological unit: a species or cultivar assigned to a space with a layer role (canopy, understory, shrub, perennial, groundcover), a quantity, a spacing, and a succession profile describing its form and behavior in years one, five, and ten. Plantings reference exactly one space and any number of care tasks.
The Surface is the ground unit: paving, lawn, mulch, decomposed granite, or water. Each surface records material, pattern, slope range, and drainage direction, and references the drainage node it sheds to.
The WaterPath is the hydrologic unit: an ordered sequence from inlet to outlet, swale, rain garden, basin, overflow, and finally the exceedance path when the system is exceeded. WaterPaths cross spaces and surfaces and are the connective tissue of the model.
The CareTask is the maintenance unit: a seasonal action with a month window, a method, a tool constraint (never sheared, cut back to ground, mown once at a named height), and the entity it applies to. CareTasks are first-class content, not appendix prose.
The invariants
Four invariants keep the model honest, and every write is validated against them.
First, every space resolves its water: each space references at least one WaterPath inlet or declares itself exempt with a reason. Orphaned water is the most common silent failure in landscape documentation, and the schema rejects it at write time.
Second, every planting carries a succession profile. A species without a year-five and year-ten description is a photograph, not a design, and the model refuses photographs.
Third, every CareTask references an existing entity and a month window. Care without an owner or a season is a wish; wishes are rejected.
Fourth, every change appends a dated entry with a one-line reason. Entities are never edited in place without a trace; replacement of a failed species, division of an overgrown grass, and regrading of a settled lawn are all history, and history is content.
Renderers: one model, many editions
With the model validated, rendering is mechanical. The client edition renders spaces as narrative rooms in walking order, with the succession profile expressed as three seasonal views and the care regime reduced to a calendar card. The contractor edition renders the same spaces as surface and WaterPath schedules grouped by trade, with planting quantities resolved per zone. The municipal edition renders WaterPaths as the stormwater narrative, hiding horticulture entirely except where a care task protects an inlet.
Because every edition reads one validated model, they cannot contradict each other. Change a swale slope and the client narrative, the contractor schedule, and the municipal stormwater paragraph update in the same release. That single-source property is the entire value proposition.
The asset pipeline
Visuals are content and get the same rigor. Each image registers against the space it illustrates, carries a caption restating the space's intent, and ships with a platform-neutral description. The pipeline enforces three rules: no embedded text, because text cannot be localized or restyled; no people, because landscape visuals must stay about places and plants; and a fixed aspect and byte budget so all five publication targets render identically.
A healing garden illustration, for instance, registers against its spaces and the accessibility obligations that shape the path. When the path geometry changes, the pipeline flags the image for review. The picture stays honest because the model says so.
Why this matters beyond the studio
The same architecture serves botanical gardens, campus grounds, park systems, and municipal streetscapes: any domain where living components, water, and seasonal labor intersect. Model the entities, declare the invariants, render per audience, register the visuals. The landscape stops being a drawing that ages and becomes a system that stays true. That is what Shapezo means by shaping content: not prettier prose, but a structure that makes inconsistency expensive and consistency free.
Top comments (0)