Webflow

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me a website that replaces Webflow — and know exactly what the verdict means.

What you are paying for is **a visual editor that is safe for a designer**: change the layout without producing broken markup, with hosting attached. The honest replacement is not another builder — it is a static site generator with a small content editor, which produces cleaner, faster output and costs nothing to host. What you give up is the canvas, and that loss is real if the person maintaining the site does not write code.

STACK
- Astro, static output where possible and a Node adapter where a form needs a server
- SQLite through better-sqlite3 for the content editor and form submissions
- Vanilla CSS and a little vanilla JS. No client-side framework
- Caddy in front

THE CONTENT LAYER, WHICH IS WHAT REPLACES THE CMS
- Content types defined in code — a page, a post, a case study, a team member — with typed fields
- Content stored as Markdown files with front matter, or in SQLite with a simple editing screen per type if somebody non-technical maintains it
- One screen per type: the fields, a preview, and publish. That is the whole editor, and it is a day's work per type
- A published change triggers a rebuild, or is served immediately if the site is server-rendered. Say which, because it changes the deployment story

THE SITE
- Sections as components taking content from data rather than embedding it: hero, features, gallery, testimonials, pricing, FAQ, contact
- Under 100KB for a page including the font, rendering complete in a second on a phone over a poor connection. A canvas builder rarely achieves that, and it is the quiet advantage of doing it this way
- Responsive from 320px, nothing hidden to make a narrow layout fit, nothing clipped, no horizontal scrolling

TYPE AND COLOUR
- One self-hosted variable font as WOFF2, subset to the characters used. Never from a third-party CDN
- Two backgrounds, two text colours, one accent, one border, every pair measured against WCAG AA rather than chosen by eye
- One size scale and one spacing scale. That constraint is what makes a hand-built site look designed rather than assembled

WHAT A BUILDER GIVES YOU FREE AND YOU MUST NOT SKIP
- Open Graph and Twitter tags with a share image generated at build time from the page's title
- A favicon set from one source image at the sizes actually used
- JSON-LD for the page type, a sitemap, robots.txt, canonical URLs, and a 301 for every changed path
- Semantic HTML: one h1, real landmarks, labels tied to inputs, visible focus rings, `prefers-reduced-motion` honoured on every animation
- Images with dimensions set, served as WebP or AVIF with a fallback, lazy below the fold, resized to the sizes actually used
- A link checker in CI, so a dead link fails the build

INTERACTIONS
- Scroll-driven animation and view transitions are CSS features now. Use them rather than a library, and restrain them — the reason builder-made sites often feel heavy is that everything moves
- Every animation respects reduced motion, completely

THE FORM
- Fields defined in data, validated on the server, stored in SQLite and emailed on
- A honeypot and a minimum time on form, plus a rate limit per address hash. No third-party form service, no captcha sending your visitors elsewhere
- Works without JavaScript: a plain POST, a redirect, a message

E-COMMERCE, IF YOU NEED IT
- Do not build a shop into this. Use a hosted checkout with the price computed on your server from a product identifier — never from the page — and keep the site static

DEPLOYING
- Built in CI on every merge, deployed as static files
- Cache headers: hashed assets immutable, HTML short
- A content security policy strict enough to forbid third-party scripts, which is easy because there are none
- A one-line deploy script and the domain setup written out

WHAT MATTERS MOST
Deciding honestly who maintains the site. If it is you, this is faster, cheaper and better in every measurable way. If it is a designer who will not touch a repository, build the content editor properly first — that screen is the whole difference.