# Build brief — a focused alternative to Wix

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

## Context

**Wix** — Website builder with templates, AI tools, ecommerce, bookings, and apps. It currently costs $29/mo.

A custom site is buildable; Wix as a platform includes editor, templates, apps, ecommerce/bookings, hosting, domains, and a huge long-tail feature surface.

This brief describes a focused, single-operator replacement for the part of Wix 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

Build the specific site directly with a framework or static generator and deploy it with forms/bookings/payments as needed.

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

## Requirements

### Functional

- Hosting.
- Domain/DNS.
- Template/theme.
- CMS.

### Data and integrations

- Form/payment/booking APIs if required.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### 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 website for my business to replace Wix · the one site I need, not a site builder. Requirements:

- An Astro static site: home, services, about, contact. Copy lives in Markdown and
  YAML data files so text edits never touch layout code.
- One mobile-first stylesheet with CSS custom properties for brand colors and type.
  No CSS framework, no page-builder abstraction.
- Contact form POSTs to a small Express handler: emails me via SMTP creds in .env
  and appends to data/messages.jsonl. Honeypot for spam.
- SEO basics at build time: sitemap.xml, robots.txt, per-page title/meta/OG tags,
  and a JSON-LD LocalBusiness block with hours and address.
- npm run build then rsync dist/ to my VPS, served by Caddy with automatic HTTPS.
- No accounts, no telemetry, no admin panel; content edits are git commits.
- If I need appointment booking, link to my scheduling tool; do not build a booking
  engine into this site.
- Out of scope: drag-and-drop editing, the app marketplace, and ecommerce. If the
  business needs a real store, that is a Shopify problem, not this build.
- README: DNS records, Caddy snippet, and exactly which files to edit for common
  copy changes.

## 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:

- Drag-and-drop editor.
- App marketplace.
- Ecommerce/bookings.
- Templates.
- Reliability at the vendor's scale is an operations problem, not a prompt.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- 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: medium. No independent one-shot implementation is linked yet.

## Prior art

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

- [GrapesJS](https://github.com/GrapesJS/grapesjs) — Open-source web builder library for visual page editing

---

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