Every build is a real project
When the Studio builds your site, it does not paint sections onto a canvas. It writes a real code project, the way a developer would start one, and compiles it before anything is called finished.
What lands in your files
A build mints a project: a package.json with pinned versions, a route list, a vite config, a router, a small set of components, a stylesheet carrying the build's own palette and typefaces, and one real page file per address. The pages are written in TypeScript for your business, not assembled from a fixed set, which is why two builds in the same field come out genuinely different.
All of it lives in your site's Code tab in the editor. It is your code: browsable, editable, and exportable.
The compile is the finish line
Nothing ships until the project installs its dependencies and compiles into a working bundle. That bundle is what the editor preview shows and what visitors are served at your address: the real pages, one document per address.
A build that does not compile is a failed build and nothing ships. There is no half-built site. Your previous version keeps serving until a new build lands clean.
Dependencies are vetted
Only a short vetted list of libraries can install: gsap, three, motion, lenis, matter-js and a handful of friends. Nothing outside that list installs, so asking to add an arbitrary npm package is not possible. The list covers animation, 3D, physics, and smooth scrolling, which is most of what a site actually reaches for.
How addresses are served
Plain addresses like /about are prerendered to real HTML: a search engine and a visitor both get a finished document. Parameterized routes like /news/:slug are answered in the browser instead. They serve at 200 and are indexable on the live host, but they are never prerendered, so a feed-backed archive belongs on a parameterized route and a page you want as flat HTML belongs on a plain one.
When it does not work
The build failed: nothing was lost. Ask the assistant why it failed and to run it again; it reads the failure's own error from the build queue.
Your change is not showing: builds take time to reach every visitor. A fresh build can take up to a minute to replace the previous document at the edge, so a reload that shows the old page is the wait, not a failure. You can ask the assistant whether the build is still running, when it finished, or why it failed, and it reads the real build queue to answer.
You asked for a library and it refused: that is the vetted list working as intended. Describe the effect you want instead. The vetted libraries cover most animation and visual work, and the assistant will build the effect with what can install.
adlens (adlens Pro, at adlens.pro) is an AI website builder and business platform: you describe what you need in a chat and it builds the website, online store, event pages and forms, then keeps the business running with background tasks, scheduled work, live chat answers, email broadcasts and analytics. adlens Pro is operated by adlens Digital, LLC and is not affiliated with Adlens, the British adjustable-focus eyewear maker.