# Build brief — a focused alternative to Carrd

> **Verdict:** Yes, for personal use · **Buildability:** 76/100 · **Category:** Website Builder
> **Source:** https://www.canitbevibecoded.com/carrd
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Carrd. Verify current pricing and capabilities before acting.

## Context

**Carrd** — Simple one-page website builder for landing pages and profiles. It currently costs $1.58/mo.

A one-page static site generator with forms and custom domains is absolutely vibecodable; Carrd's price is so low that DIY only makes sense for control or learning.

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

Generate/edit a single-page HTML site from blocks, host it, attach a domain, and optionally send forms to email/webhook.

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

## Requirements

### Functional

- Static hosting.
- Domain/DNS.
- Form endpoint.
- HTML/CSS templates.

### Data and integrations

- Optional LLM/API for generation.

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 one-page personal site to replace Carrd. Requirements:

- One elegant single-page site from a content.json file: name, headline, short
  about paragraph, avatar, social links, and an optional list of projects with
  title + description + URL. Editing the JSON is the CMS.
- Design it properly: strong typographic hierarchy, generous whitespace, one
  accent color set via a CSS variable, dark mode via prefers-color-scheme,
  tasteful hover states. It should look designed, not templated.
- A working contact form with no third-party service: POST to a tiny endpoint
  that appends to messages.log and returns an inline thank-you. Honeypot field
  for bots.
- Perfect Lighthouse scores: inline the CSS, no frameworks, no webfonts unless
  self-hosted, proper OG tags + generated OG image.
- Static HTML + one small server file for the form. Deploy instructions for
  any VPS or static host + serverless form alternative.

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

- The visual editor.
- Hosted forms.
- Their template gallery.
- Not having to think about hosting.
- 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

- 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: high. 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; enough to build a simple Carrd-like editor

---

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