Templates constrain the story
Fixed sections and rigid grids force the work into a layout it was never designed for, and custom structure means fighting the builder at every step.
Website Builder for real content sites
Turn your studio and its work into a site you can inspect and shape
Describe the pages, the story, and the work you want to show. E-Code turns that into a responsive marketing site in editable source code. Inspect every file, run the site in Preview, refine it through the Agent, and publish supported static builds to a live URL.
Start from the pages you already have in mind. Source files, the running Preview, and publishing controls stay visible as the site evolves.
Selected work
Buildings shaped by light, place, and material.
A responsive portfolio site that presents projects, the studio, and an enquiry path in one clear journey.
Featured projects
- Coastal House, BiarritzFeatured
- Riverside Pavilion
- Atelier Extension
This inline demonstration shows a portfolio grid, studio profile entry, and an enquiry form in one responsive layout.
From template lock-in to source you control
Site builders look easy until the content and the brand fight the template
A studio needs a site that shows its work exactly the way it wants. Template builders start fast, then constrain layout, typography, and structure, and the exported result rarely maps to code the team can keep evolving.
Content and code drift apart
Marketing tools hold the copy, a separate export holds the markup, and there is no single source the team can inspect, version, and change with confidence.
Hand-off leaves you dependent
When a freelancer or agency ships the site, the smallest change waits on someone else, and the underlying code is often unavailable to inspect or export.
E-Code starts from the pages you describe and produces a responsive site in real source files. You inspect the markup, run it in Preview, and request the next change without leaving the code behind.
One prompt starts the site
Describe the pages, not the framework
The request below reads like a note from a studio owner. The four items map its implementation scope in real source files, not a locked template.
Example prompt
Build a showcase website for my architecture firm, with a portfolio, contact page, and blog.
- 01
Responsive pages
Home, portfolio, project detail, studio, and contact pages render across desktop, tablet, and mobile from real components and routes.
- 02
Structured content
Projects, images, studio details, and enquiries are modeled as editable content the team can extend without breaking the layout.
- 03
Working contact flow
The enquiry form validates input and exposes a submission hook in code. Connect that hook to your chosen form or email service before accepting real enquiries.
- 04
Preview and publishing
E-Code runs the site in Preview across screen sizes. Supported static builds continue through guided publishing to a live URL; other projects stay exportable for any host.
The site-building workflow, captured in the IDE
See how the prompt, Agent, files, and Webview stay together
The App Builder page shows a captured, real E-Code workspace — the prompt, the agent’s plan, the generated files, and the running Preview — for a booking application. The same build loop applies to a content site like this one.
This first capture shows the real booking prompt, the Agent plan, the project tree, and the working salon dashboard together inside the E-Code IDE.
Open the booking-workspace evidence at full size
The second capture records the follow-up prompt used to diagnose a React context error while keeping the booking Preview visible for verification.
Open the booking-workspace evidence at full sizeWhat you receive
A responsive site you can inspect, export, and keep evolving
The project stays inspectable from the first generated file through Preview and export. Supported static builds add a live release through guided publishing without hiding the code.
Website source you can inspect
Real routes, components, styles, and page content remain readable, versionable, and exportable as a complete project.
Visible content schema and form adapter
Project entries, media fields, studio details, and the enquiry hook live in the code. Wire them to your CMS, database, and delivery service before using real content or submissions.
A responsive site running in Preview
Open the portfolio and contact journey in the active Preview, then inspect its desktop, tablet, and phone layouts while you refine the site.
Guided release for supported static sites
When the website matches a supported static build, E-Code takes it through the guided publishing flow without hiding the source.
An E-Code URL or an exportable server project
A supported static site receives a live E-Code URL after publishing. If the project needs a server runtime, export the source and deploy it with your chosen host.
Keep briefing the Agent
Continue the conversation to add a case study, reshape the navigation, or revise a form, then review the change against the running site.
Built for real content sites
Everything a studio site needs, in code you control
The Website Builder path keeps design intent, content, and publishing in one inspectable workflow.
Portfolio and case studies
Present projects with images, detail pages, and structured metadata.
Content you can edit
Copy and media live in editable files, not a locked builder database.
Forms and enquiries
Contact and lead-capture interfaces with validation plus an explicit integration point for your delivery service.
SEO and social metadata
Titles, descriptions, and Open Graph tags generated per page.
Responsive by default
Layouts adapt from wide desktop to phone without a separate mobile build.
Keep the source accessible
Export the project or publish supported static builds while retaining editable source files.
Who builds with it
Sites teams ship with the Website Builder
From a studio portfolio to a product launch page, the same loop produces a real, responsive site.
Studio and portfolio sites
Architects, designers, and agencies presenting selected work.
Company and marketing sites
Multi-page sites with a clear story, services, and contact paths.
Launch and campaign pages
Focused pages with lead capture and social metadata ready to share.
Docs and content surfaces
Readable, structured content sites that stay easy to update.
Common questions
Website Builder, answered honestly
What the Website Builder path produces, and where its boundaries are.
Do I get real code or a locked template?+
You get editable source files — components, routes, styles, and content — that you can read, version, and export. There is no proprietary template lock-in.
Is the site responsive?+
Yes. Layouts are generated to adapt across desktop, tablet, and mobile, and you verify them in Preview at each size before publishing.
Can I publish to a live URL?+
Supported static builds publish to a live URL through guided publishing. Other projects remain exportable for your own hosting workflow.
Can I connect a CMS or database?+
The generated content model is code you can extend and wire to external services. The inline demonstration on this page uses fictional data and no connected backend.
How do I change the site later?+
Edit the files directly or ask the Agent for the next change and review the diff against the running Preview.
Website Builder for real content sites
Describe your site and see it running
Turn the pages you have in mind into a responsive site in real source code, run it in Preview, and publish supported static builds.