SMF·WEBFLOW
Can a prompt replace Webflow?
Website builders — visual website builder
Exhibit tracking slip
Verdict
A block-based static site generator — content as Markdown and YAML, a design-tokens file for consistent styling, a working contact form — is a real, if unglamorous, weekend build. What doesn't come with it is Webflow's actual product: a visual designer with pixel-level control, animations, and a workflow a non-developer can use to make changes without touching a file.
Exhibit A — The prompt
Received on30.07.2026Build a static site generator (Eleventy is a solid choice) where a page is defined as a YAML file listing content blocks in order — hero, feature grid, testimonial, pricing table, FAQ, call-to-action, footer — each block rendered from its own template partial, so building a new page means editing YAML, not HTML. Add a lightweight 'CMS' with no actual CMS: blog posts and case studies as Markdown files with front matter, with listing and detail pages generated automatically at build time. Put all colors, type scale, and spacing into one design-tokens file so a full restyle touches exactly one place. Make every block responsive by default, tested at both a small phone width and a wide desktop width. Wire the contact form to post to a small server endpoint that emails the submission through a real email service. Generate a sitemap and per-page meta and social preview tags automatically at build time.
Do not build a visual drag-and-drop designer or a non-developer editing workflow — those are Webflow's actual product. If visual, no-code editing genuinely matters, the honest move is self-hosting an existing open-source visual builder rather than writing one from scratch.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the visual drag-and-drop designer
- B.2 built-in animations
- B.3 a client-friendly editing workflow for non-developers
- B.4 a templates and component marketplace
- B.5 hosted forms
Prior art
Exhibit C — Why people still pay: editor/CMS/hosting
A designer can ship and maintain a production site without engineering every component themselves — the value is the visual workflow, not any single page it produces.
Questions
Can I import my existing Webflow site?
Not structurally — Webflow doesn't export to a format this build can read. In practice this means rebuilding pages as YAML block lists and copying over the actual content and images, which is real work but not a blank start.
Will it work on my phone?
The published site, yes — every block is built responsive by default. Editing content is a YAML, Markdown, and git workflow, which isn't a phone task.
What does it cost to run?
Static hosting is often free or a couple of dollars a month, since there's no database — noticeably cheaper to run than to design and maintain.
What's the one thing that doesn't survive the rebuild?
Visual, non-developer editing. Every future content or layout change here goes through YAML, Markdown, and a deploy; a designer or client who isn't comfortable with that workflow loses the ability to make changes themselves.
Related tools
Receipt