docs · deprecated
Bricks and reusable composition
Understand the earlier composition contract and how it relates to current Foundry layers.
Applies to v0.2.4
Component pins for v0.2.4
| Component | Role | Version |
|---|---|---|
| core | runtime | v0.1.20 |
| theme-shield | theme | v0.1.15 |
| starter | reference | v0.1.3 |
| docs | reference | v0.1.4 |
| distribution | tooling | v0.3.2 |
| restricted-component-1 | consumer-reference | v0.1.10 |
| restricted-component-2 | consumer-reference | v1.1.21 |
Foundry supports an alternate “bricks” structure:
bricks:
hero:
block: hero
content: ...
stats:
block: stats-grid
content: ...
bricks_order:
- hero
- stats
If sections is empty and bricks exists, Foundry will render bricks in bricks_order (or map order if not provided).
Use this when you want reusable named blocks and ordering without duplicating section objects.