Figma is a sandbox, not a website: the design/development boundary
The Figma page and the Elementor page look identical on screen — but one of them is 'only viewable in your account or via a link.'
Two lessons build the boundary from both sides. What Figma LACKS is what makes a website real: code, hosting, a database, logic — 'it's like a design sandbox.' Figma Sites and converters exist but move layout and styling, not function. What Figma OFFERS is exactly what page builders make hard: friction-free ideation, real-time client collaboration, and stability ('Figma changes far less than page builders' — peace of mind as a feature).
The deeper argument is neurological: 'it's just very hard to activate both brain sides at the same time' — designing while building forces constant creative/logical context-switching, which is why design-first beats design-in-the-builder. And the boundary cuts both ways professionally: ten years in, he has never learned code ('don't listen to people who say that you should'), because design and development are separate, equally chargeable skills.
The side-by-side demo: a converted Elementor page against its Figma original — visually twins, functionally a website and a picture of a website.
The whole course rests on this line: every later phase (sitemap, direction, design) happens in the sandbox BEFORE the builder, on purpose.
Figma prototypes are almost-websites.
Clickable prototypes simulate navigation only — 'don't think that what we do in Figma is real.' Converters move pixels, not function.
Figma is a design tool, not a development tool... it's like a design sandbox.
It's just very hard to activate both brain sides at the same time.
['Same boundary as your own pipeline: the YAML records are the sandbox; build_site.py is the builder. Design the record, then render.']
Go deeper
In one line: Figma = strategic design layer: free-form, collaborative, stable, and deliberately non-functional. Websites get their function later, in the builder. Design-first exists because ideation and implementation compete for the same brain.
'Figma is a design tool, not a development tool... a design sandbox' (l2691671 0:00:00)
'Easier for our brain to first focus on design... hard to activate both brain sides at the same time' (l2691671 0:04:01)
Ten years, no code: design and development are separate paid skills (l2691671 0:10:07)
Tool-market snapshot: Photoshop → Sketch → Adobe XD (killed) → Figma, with Penpot the open alternative (l2691672 0:00:00)
Stack declared: Figma + Hostinger + WordPress + Elementor; wordpress.com explicitly warned against (l2691672 0:08:05)
Open any design you've made in a page builder and ask what percentage of your session went to layout decisions vs. builder mechanics — that mechanical share is what the sandbox removes.
▶ Watch this taught:
Answer from memory first — the recall attempt is what makes it stick. Then reveal.
A client asks you to 'just build it in Figma so it's done.' What's wrong?
Nothing in Figma is done — no code, hosting, data, or logic. Figma output is an agreement artifact; the build is a separate phase and a separate skill.


