Concepts

VoodBuilder is easier to learn when three ideas stay separate: where work happens, which edition you bought, and how the canvas stores content.

Where work happens

flowchart TD
  A[Filament admin] --> B[Visual editor]
  B --> C[Public site]
  A -->|Pages Menus Layouts Theme Studio| B
  B -->|Saved HTML CSS| C
  C -->|Chrome theme SEO search consent| C

Layer	Job
Admin	Structure the site — pages, menus, layouts, Theme Studio, companion resources
Editor	Compose and style content; Content / Style / Dynamic sidebars
Public	Serve published pages with chrome, SEO, access, and runtime companions

Details: Architecture.

Which edition you bought

flowchart LR
  C[Community] --> D[Developer]
  D --> A[Agency]

Edition	Unlocks
Community	Core site platform + Vmedia + Vcookiebar (free)
Developer	Elements · Dynamic Data · Templates
Agency	Everything in Developer · Components · Dynamic API · Popups

Same editor across all three. Editions change companion entitlement, not a different product.
Details: Editions at a glance · full matrices in Editions.

How authors edit content

Mechanism	Sidebar	Edition
Declarative `data-vb-*` fields on section HTML	Content	Any section that ships with markers
Tailwind / theme tokens	Style	All
Eloquent / API bindings	Dynamic	Developer+ / Agency
Official catalog tiles	Library modal	Developer+ (Elements)
Your saved sections	Components tab	Agency

Walkthrough: Building sections.

Stack note

Runtime stack and the single mention of the canvas library live under Foundations.