Design: The Layers & Guilds

Once you've mapped your site (see Planning Your Site), design starts from the top down. Work through each layer in order, canopy first, and ask the same two questions at every layer: what do I want to harvest from here, and what does it need from its neighbors to thrive?

The seven layers

1. Canopy — the tallest trees, forming the top of the system. Full-size fruit and nut trees go here.
2. Understory — smaller or dwarf trees that fill the gaps the canopy leaves open, taking advantage of partial shade.
3. Shrub — berries and shrub-scale food plants, filling the space below the trees.
4. Herbaceous — perennial vegetables and herbs, non-woody, filling in at ground level and slightly above.
5. Groundcover — low, spreading plants that cover bare soil, hold moisture, and crowd out weeds so you largely don't have to.
6. Root — crops growing underground, using space nothing else is using.
7. Vine — climbers that use the vertical space on trunks and structures rather than needing their own.

Each layer is a distinct planning decision. A common beginner mistake is planting the canopy and calling it done — a food forest with only a canopy layer is an orchard, not a food forest. The other six layers are what make the system self-sustaining rather than just a collection of fruit trees.

What a guild actually is

A guild is a small group of plants placed together on purpose because they help each other. The classic version has a few common roles:

• A nitrogen fixer (often a legume tree or shrub) that pulls nitrogen from the air into the soil, feeding everything planted near it
• A nutrient accumulator — a deep-rooted plant that pulls minerals up from lower in the soil where shallower-rooted plants can't reach
• A pest deterrent or pollinator draw — something aromatic or flowering that either confuses pests looking for your food crop, or brings in the insects that pollinate it
• The food-producing plant itself, which is the actual point of the guild — everything else exists to support it

You don't need every role filled to get value from grouping plants this way. Even a simple pairing — a fruit tree with a nitrogen-fixing shrub planted near its base — is a real guild and a real improvement over planting the fruit tree alone.

A worked example: Hawaiʻi, wet-tropical

This is drawn from real, already-producing planting in South Kona, not a textbook example:

• Canopy: breadfruit or citrus
• Understory: banana, which tolerates the partial shade under a canopy tree well
• Shrub: coffee, which does well in dappled light
• Herbaceous / root: kalo (taro) and ʻōlena (turmeric) — both real, currently producing crops on the reference site this content is drawn from
• Groundcover: sweet potato, which spreads to cover soil while also producing a harvest
• Vine: passionfruit, trained up a canopy tree's trunk rather than a separate structure

That's a functioning guild stack in a single vertical footprint — six layers, each producing something, each placed with a reason.

Clear before you plant

On a site with existing invasive growth, design and clearing happen together, not in sequence — you generally can't tell what a piece of ground is actually capable of until the invasives are out. Guinea grass, Christmas berry, Cat's claw, and similar aggressive invasive species common in Hawaiʻi will outcompete a young planting before it has a chance to establish. Real example: the South Kona site this content draws from cleared Guinea Grass, Maile Pilau, Cat's Claw, and Christmas Berry before kalo, ʻōlena, and koa went in — the clearing wasn't a side task, it was the first phase of the design.

Next

Once the layer plan and a first guild or two are sketched onto your site map, the next real question is what the ground underneath all of it needs — see Soil, Water & Establishment.