Editing your website by hand

Everything the assistant builds is written in ordinary source files, and you can open and edit those files yourself. This section is for the people who want to.

You do not need any of it. A website built entirely through conversation is a complete website, and nothing here changes how the assistant works. But if you write HTML, if you have used a static site generator before, or if you simply want to know what the assistant is actually doing, this is the layer underneath.

What your website is made of

Every Max AI website is a set of Blade templates — the template language from the Laravel framework — compiled into a plain static website. You write pages, layouts, and reusable sections; the platform compiles them into HTML after every change; visitors get flat files that load fast and cannot break.

Three things follow from that, and they are worth holding onto:

• The templates are the truth. The HTML your visitors receive is generated. Edit the templates, never the compiled output.
• You and the assistant share one set of files. The assistant sees every edit you make, and you can see every edit it makes. There is no separate "code version" of your website that drifts from the conversational one.
• Nothing runs on a server. A static website has no request-time code, so the Blade you write is restricted to the part of the language that compiles ahead of time. That boundary is documented precisely, and the platform tells you when you cross it.

In this section

• Developer mode — the switch that reveals the code editor, the file tree, and the revision history, and everything each one does.
• Building with Blade — the source tree, how pages become URLs, layouts, components, control flow, and styling.
• Site data and collections — site.json, data collections, the Content place, and dynamic pages that generate one URL per entry.
• Editable sections — giving a section a companion .yml file so Edit mode can offer proper fields for it.
• File history and undo — looking at a file's earlier contents and putting one back.
• Blade syntax reference — every supported directive in one place, what is deliberately unavailable, and how to fix a template that will not compile.

A safe place to experiment

The builder is not a live website. Your edits land in a draft, the draft is what the preview and your free dev address show, and your custom domain keeps serving the last version you published until you press Publish again.

On top of that, every save is recorded. The code editor keeps a revision history for each file, so an edit that goes wrong is one click away from being undone — see File history and undo.

Break things. That is what a draft is for.