Code Builder overview

Code Builder is a code editor inside the site builder for projects that are easier to write than to assemble from blocks: a custom landing page, a configurator, a dashboard, a members area. Praisma builds each change in a secure sandbox and shows the result in a live preview. You can write the code yourself, use the built-in agent, or connect an assistant over MCP.

Project types

HTML: plain HTML, CSS and JavaScript files, no bundler.

React: a bundled React app. You may importreact,react-dom,react-router-dom,clsxand theapproved libraries. Multi-page apps usereact-router-domwith thebasenameread from the injected<base>tag.

Rules that keep builds working

Userelativelinks for local files (brand.css,assets/logo.svg,about.html), never a leading/: the project can be mounted under any path of your site.

Browser code and local files only: no secrets, remote scripts, package changes or server code.

A failed build keeps the previous preview, so a mistake never blanks the page.

Your brand as the design system

Every project has a platform-managed brand.css with your brand's --brand-* custom properties and fonts, regenerated on every build. Import it once and use the variables instead of hard-coded colours, fonts and sizes. Colour schemes are available as --brand-scheme-{name}-bg, -text, -border, -radius, -shadow, -button-bg and -button-text for page, section, section-alt, section-contrast, accent, container and card.

/* styles.css */ @import "./brand.css"; .hero { background: var(--brand-scheme-section-bg); color: var(--brand-scheme-section-text); } .cta { background: var(--brand-scheme-accent-button-bg); color: var(--brand-scheme-accent-button-text); }

Preview and publish

Each project has one private preview address that always shows the latest build and reloads itself when a newer one is ready. Publishing needs a ready build and permission to publish the site.

A backend without tokens

Apps reach your CMS, media library, shop and visitor accounts through window.Praisma. You declare what the app needs in praisma.json and a site manager approves it before publishing. See praisma.json and the window.Praisma reference.