# Build brief — a focused alternative to Webflow

> **Verdict:** Partly, if you narrow it · **Buildability:** 40/100 · **Category:** Website Builder
> **Source:** https://www.canitbevibecoded.com/webflow
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Webflow. Verify current pricing and capabilities before acting.

## Context

**Webflow** — Visual website builder and CMS for marketing sites. It currently costs $25/mo.

A personal visual website builder is possible with existing editors, but Webflow's CMS, designer, hosting, animations, components, SEO, and client workflows are deep.

This brief describes a focused, single-operator replacement for the part of Webflow that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Use a visual editor or generate static pages from blocks, publish to hosting, and add a small CMS.

- Create a constrained editor with preview, publishing, and reusable sections.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Visual builder/editor.
- CMS database.
- Static export/build.
- Hosting.
- Asset manager.
- Auth.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a block-based marketing site generator to replace Webflow, for my own sites. Requirements:

- An Eleventy static site where a page is a YAML file listing blocks: hero, feature
  grid, testimonial, pricing table, FAQ, CTA, footer. Each block is a Nunjucks
  partial; building a page means editing YAML, not HTML.
- CMS collections without a CMS: blog posts and case studies as Markdown with front
  matter, listing and detail pages generated at build time.
- One design-tokens file (CSS custom properties for colors, type scale, spacing) so
  a restyle touches exactly one file.
- Responsive by default: every block works at 360px and 1280px, images via
  @11ty/eleventy-img.
- Forms POST to a small Express handler that emails me via SMTP creds in .env.
- Build to dist/, deploy with rsync to my VPS behind Caddy. Sitemap and per-page
  meta/OG tags generated at build.
- No accounts, no telemetry, content lives in git.
- Out of scope: a visual drag-and-drop designer and client handoff. If I truly need
  visual editing, self-host Webstudio instead of building an editor.
- README: block YAML reference with one full example page, DNS + Caddy snippet.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Designer fidelity.
- CMS.
- Hosting.
- Animations.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Reliability at the vendor's scale is an operations problem, not a prompt.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Webstudio](https://github.com/webstudio-is/webstudio) — Open-source visual website builder and serious Webflow-like prior art

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/webflow