The Design Becomes The Site. Not A Picture Of It.

Functionality ships as self-contained plugins from a curated library covering workflow automation, data and analytics, third-party integrations, security and access control, and content management. Each one is documented, compatibility-checked, and installs by copying a folder and registering the module.

Copy the folder, register the module, deploy. Every module follows the same conventions, the AdvantageModule base class, fetch() rather than postbacks, a bwa- CSS prefix, WebAPI controllers and a complete admin dialog, so it behaves like everything else in the admin once installed.

They are a curated, verified catalogue rather than a community marketplace. There are 88 modules organised by business need: workflow automation, data and analytics, third-party integrations, security and access control, and content management - each with compatibility checks, full documentation and expert support.

Yes. Designers work in Figma, and BWA Web Studio converts React and Tailwind designs into production ready BWA modules using Babel AST parsing with a zero-regex policy, so the conversion understands the code structure rather than pattern matching it.

No, design to production runs as one pipeline. Web Studio takes the design through to deployable modules, which then behave like any other module in the page builder, so the handoff from design to build is not a rewrite.

A whole multi-page design project imported in one go rather than a page at a time. A dealer site might be twenty-five pages; a pack brings all of them in together, gives you a page menu, and lets you set the brand and the business's own details once for the entire pack. Each page then goes through the same conversion pipeline as a single-page import.

No. The automotive pack is the blueprint, but the loader itself is sector-agnostic. Another vertical is authored the same way, design the pages, then ship a pack manifest declaring the sector, the sample identity strings the pages contain, and each page's slug, title and entry point.

Settings are split deliberately. Pack-wide covers brand, archetype, design system, chrome, corner language and the business's own details: name, tagline, phone, address and an uploaded logo. Change any of those on one page and every other page follows. Per-page covers only each band's treatment, whether it is shown, and the band order.

Yes, when the design has one. Each page is rendered twice, once at desktop width and once at phone width, so the design is driven into its own mobile state rather than just being narrowed. A design authored only at desktop width still converts, but what you get is a squeezed desktop composition, so author the mobile state if mobile matters.

The design brief is generated from the installed module catalogue rather than written by hand, so a design cannot name a module that does not exist. An upload gate then validates the pack before any conversion is spent on it. One limit worth knowing: WebStudio can confirm a module exists and is installable, but not that it is registered on a particular customer domain that lives in the tenant database and should be checked on the target domain.

Three sources, all converging on the same conversion pipeline: a Figma frame, a Claude Design or HTML project, and a multi-page Design Sector Pack. Whichever you start from, the conversion passes through a human approval step before anything is generated.

Real modules wherever it can. Web Studio reads the names in the design, section names, and above all the field names inside repeating items to bind each band to an existing module by reference. Where no module matches, the band falls back to an AI Block: it installs and works, but it does not yield a reusable module, so naming things in line with the platform's conventions is what keeps a design importing as modules rather than as blocks to rework later.

Through a Brand Corpus, a versioned snapshot of your brand's palette, typography, design tokens and approved layout patterns for the tenant. Generated content is produced against those tokens rather than against whatever the model felt like, so output inherits your brand instead of approximating it.

Yes. The Brand Corpus has a staged / live / archived lifecycle with revert, so a brand update is an auditable, reversible resource rather than an edit you cannot undo. Exactly one corpus is live at a time, and the previous one stays available to revert to.

Anywhere HTML is rendered. The shortcode engine runs as a response filter over outgoing HTML, so a token works in page modules, in editor content, and in snippets or code blocks saved from the rich-text editor, not only in places a developer wired up in advance.