SMF·DORIK
Can a prompt replace Dorik?
Website builders — websites and landing pages
Exhibit tracking slip
Verdict
The static site generator underneath is straightforward. Dorik's actual job is letting an agency hand a finished site to a client who can then change the copy without breaking the layout or calling you. Building that split — a designer surface and a much smaller client surface over the same content — is the interesting part and takes a few days. Hosting, domains and SSL handled for a dozen client sites is the part you are still paying someone for.
Exhibit A — The prompt
Received on31.07.2026Build a static site generator with two editing surfaces: a full one for the builder, and a restricted one for the client.
Projects: each site is a project with its own content, theme token file (typography scale, palette, spacing, radius, logo) and block composition. One codebase, many sites.
Block library: hero, feature grid, testimonial, logo strip, pricing table, FAQ accordion, team grid, contact form, call to action, rich text, image gallery, footer. Every block consumes theme tokens only; there is no per-instance styling. Blocks are composed into pages in order, with no free positioning.
Builder surface: add, remove and reorder blocks, choose block variants, edit all content, and edit the theme tokens. Full access.
Client surface, which is the point of this build. The same site rendered with only content fields editable — text within its declared length limits, images within declared dimensions, and link targets. No block can be added, removed or reordered; no theme token can be touched. Fields declare their constraints in the block definition, and the client editor validates against them before saving, so a client cannot paste four hundred words into a headline slot and wonder why the page broke. Every client edit is versioned with an author and a timestamp, and any version can be restored.
Output: build to static HTML with one CSS file per site generated from its tokens, responsive image sets generated at build time, and no client-side JavaScript beyond the accordion and mobile menu. Emit a sitemap and per-page meta tags editable from either surface.
Forms: the contact block emits a plain HTML form posting to a configured endpoint. Do not build a submission service; document connecting one, and make the endpoint a per-project setting.
Deployment: a build command per project producing a folder of static files, and a documented deployment to one target including custom domain and certificate setup. A per-project deploy log recording what was built and when.
Storage: content as JSON per project, in a git repository so client edits are diffable.
Out of scope: managed hosting, a template marketplace, memberships or gated content, ecommerce, and any multi-tenant login system beyond a single shared credential per project.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 hosting, domains and SSL managed for every client site
- B.2 the template marketplace and its ready-made designs
- B.3 form submissions collected without a backend of your own
- B.4 membership and gated-content features
Prior art
Exhibit C — Why people still pay: editor polish, hosting, templates, and ecosystem
Because an agency running fifteen client sites is buying operations, not a builder. Certificates renewing, forms delivering and a client editor that never breaks are worth more than any block library.
Questions
Can I export a site from Dorik?
Dorik offers an HTML export on some plans, which gives you the rendered markup but not a structure this build can consume. In practice a migration means recomposing the page from blocks, which for a small marketing site is an afternoon.
Why restrict the client editor so heavily?
Because the alternative is a support call. An agency's real cost on a small site is not building it, it is the client who moved a section and broke the layout six months later. Length and dimension limits enforced at save time prevent most of that.
What does it cost to run?
Static hosting for client sites is free or close to it on the usual providers, plus a domain each. Against a per-month builder subscription for a dozen sites this is a substantial saving — offset by the fact that renewals, certificates and form delivery are now yours to watch.
What is the one thing that does not survive the rebuild?
Operations at scale. One site is easy. Fifteen sites means fifteen domains, fifteen certificates, fifteen form endpoints and a client emailing you on a Sunday because the contact form is silently failing. That accumulation is exactly what the subscription covers.
Related tools
Receipt