Can Dorik be vibe coded?
Build a small responsive site with pages, collections, and simple forms
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Dorik, build a small responsive site with pages, collections, and simple forms. The hard boundary is hosting, cms, memberships, templates, and no-code editing polish, plus editor polish, hosting, templates, and ecosystem.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Assemble a small responsive site from sections with pages, collections, and simple forms, edit copy and media, preview breakpoints, and publish a static site to a user-owned target.
- Create a constrained editor with preview, publishing, and reusable sections.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- hosting, CMS, memberships, templates, and no-code editing polish
- large template marketplace
- managed hosting and CDN
- advanced CMS
- 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.
Why people still pay
People still pay for Dorik because the page renderer is reproducible, but customers pay to avoid becoming their own hosting and browser-compatibility team. The recurring cost buys responsive rendering, forms, domains, certificates, deploys, backups, template maintenance, and browser regressions, not just the visible interface.
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.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Dorik
Context
**Dorik** — Build a small responsive site with pages, collections, and simple forms. It currently costs $19/mo.
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Dorik, build a small responsive site with pages, collections, and simple forms. The hard boundary is hosting, cms, memberships, templates, and no-code editing polish, plus editor polish, hosting, templates, and ecosystem.
This brief describes a focused, single-operator replacement for the part of Dorik 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
Assemble a small responsive site from sections with pages, collections, and simple forms, edit copy and media, preview breakpoints, and publish a static site to a user-owned target.
Create a constrained editor with preview, publishing, and reusable sections.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Node.js 22.
Domain and deploy target.
Local images.
Data and integrations
Optional form-email API key.
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 a personal replacement for Dorik in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export; do not offer alternative stacks.
The core loop is: assemble a small responsive site from sections with pages, collections, and simple forms, edit copy and media, preview breakpoints, and publish a static site to a user-owned target.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Provide a section library for hero, proof, features, pricing, FAQ, and footer blocks.
Use a constrained design-token system rather than arbitrary CSS controls.
Allow inline text editing and local image upload with responsive optimization.
Preview desktop, tablet, and mobile widths and surface overflow errors.
Persist projects in SQLite and support a portable JSON export.
Generate a clean static Next.js output and document deployment to one target.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a plugin marketplace.
Deliberately leave out multi-tenant managed hosting.
Deliberately leave out advanced ecommerce, memberships, and agency billing.
Finish by running the tests and listing the exact commands used.
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:
Hosting, CMS, memberships, templates, and no-code editing polish.
Large template marketplace.
Managed hosting and CDN.
Advanced CMS.
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: medium. 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 designed around web standards
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/dorik
You still own the product
- 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.
Open-source prior art
Before you start
Can Dorik be vibe coded?
Partly, if you narrow it. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Dorik, build a small responsive site with pages, collections, and simple forms. The hard boundary is hosting, cms, memberships, templates, and no-code editing polish, plus editor polish, hosting, templates, and ecosystem.
What can an AI coding agent reproduce from Dorik?
Assemble a small responsive site from sections with pages, collections, and simple forms, edit copy and media, preview breakpoints, and publish a static site to a user-owned target. Create a constrained editor with preview, publishing, and reusable sections. A responsive interface with real empty, loading, success, and error states.
What will a DIY Dorik replacement still be missing?
hosting, CMS, memberships, templates, and no-code editing polish; large template marketplace; managed hosting and CDN; advanced CMS; 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 do I still own after building a Dorik alternative?
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.