Architecture
VoodBuilder runs inside your Laravel application. You design pages in Filament, edit them on a visual canvas, and publish HTML your app serves — with shared chrome, themes, SEO, and access rules. There is no mandatory third-party site host.
Three layers
flowchart TD
subgraph admin [Filament admin]
P[Pages]
M[Menus]
L[Chrome layouts]
T[Theme Studio]
X[Companion resources]
end
subgraph editor [Visual editor]
Lib[Library]
Canvas[Canvas]
Ins[Content / Style / Dynamic / Conditions]
end
subgraph public [Public site]
HTML[Page HTML + theme CSS]
Shell[Chrome layout shell]
RT[Bindings · search · consent · popups]
end
admin --> editor
editor -->|Save HTML / CSS| public
| Layer | Responsibility |
|---|---|
| Admin | CRUD for site structure and companion configuration |
| Editor | Compose content; expose sidebar settings; bind dynamic fields when entitled |
| Public | Render published pages with chrome, SEO, access gates, and runtime companions |
What is stored
| Concern | Storage |
|---|---|
| Page canvas | HTML (and related CSS) on the page record |
| Shared shell | Chrome layout records |
| Brand tokens | Theme Studio settings |
| Navigation | Nestable menu tree → public URLs |
| Declarative Content fields | Attributes and text inside the saved HTML |
| Dynamic bindings | Binding attributes resolved when the page renders |
| Saved Components | Project component library (Agency) |
| Remote Elements | Catalog fetched by your app; tiles become normal HTML once imported |
Companions as modules
Core VoodBuilder is modular. Paid and Community companions register Filament plugins that activate editor features and admin resources. Installing a Composer bundle without registering a plugin leaves that surface inactive. Licence checks (Anystack / VoodFlow APIs) decide whether entitled capabilities are available.