SMF·UNICORN-PLATFORM
Can a prompt replace Unicorn Platform?
Website builders — websites and landing pages
Exhibit tracking slip
Verdict
The thing worth copying here is the exit: whatever you assemble comes out as a real static project you own, so the builder is a starting point rather than a place your site lives. Building a generator that emits clean, idiomatic source rather than a runtime blob is the interesting constraint, and it is what makes this a multi-day project instead of an evening one. The hosted convenience — publish, domain, forms, done — is the part you are choosing to give up.
Exhibit A — The prompt
Received on31.07.2026Build a landing-page composer whose primary output is a clean static project the user can maintain without this tool.
Component set, fixed and small: hero, feature grid, feature with image, logo strip, testimonial, pricing table, FAQ accordion, call to action, footer, and a rich-text block. Each has two or three variants. Positioning is not a user control — layout comes from the component and the theme.
Theme: a token file with a type scale, palette, spacing scale and radius. Components reference tokens only.
Editor: a page is an ordered list of components. Add, remove, reorder by drag, choose a variant, and edit content inline. Breakpoint preview at three widths with an overflow check that flags any component whose content breaks its container at the narrow width.
Export, which is the point of this build. Emit a complete Astro project, not a bundle:
- One `.astro` component file per component type used, with real props and readable markup — semantic elements, no wrapper soup, no generated class names like `c-1a2b3c`.
- The page as a file composing those components, in order, with content passed as props rather than baked into the markup, so content is editable separately from layout.
- One CSS file generated from the theme tokens, with custom properties at the root so a developer can restyle without touching components.
- Images copied into the project and referenced through Astro's own image handling, with responsive sets generated at build.
- A `package.json`, a README explaining the structure, and a `.gitignore`. Running the documented command must start a dev server.
The test that matters: a developer who has never seen the builder should be able to open the exported project, find the headline, change it, and understand where the styling comes from, within five minutes. Write that as an acceptance criterion in the README and check the output against it.
Re-export: emit into a directory the builder owns and never touch files outside it, so a developer who has added a route or a component keeps their work. Document plainly that once the exported code is edited, the round trip is one-way — that is the honest consequence of code ownership and pretending otherwise is how these tools lose people's work.
Forms: emit a plain HTML form posting to a configured endpoint. Do not build a submission backend; document connecting one.
Storage: the page definition as JSON in the project repository, so it diffs.
Out of scope: hosted publishing, a template marketplace, a CMS or blog, AI copy generation, and any account system.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 hosted publishing with a domain and certificate attached
- B.2 the template library and its designed starting points
- B.3 form submissions collected without a backend of your own
- B.4 the AI copy assistance built into the editor
Prior art
Exhibit C — Why people still pay: editor polish, hosting, templates, and ecosystem
Because most people who buy a landing-page builder never export anything. They want the page live this afternoon, and hosted publishing is the feature they are actually paying for.
Questions
Can I import a Unicorn Platform site?
Its paid plans export static code, which you can keep and host. That code does not import back into this builder's format, so the visual design is rebuilt if you want to keep editing visually — which is the same one-way trade this build makes explicit.
Why insist the exported code be readable?
Because that is the entire proposition. An export that produces a minified bundle with generated class names is technically an export and practically a lock-in, since nobody can maintain it. The five-minute test in the prompt exists to keep the output honest.
What does it cost to run?
The builder is local and free. The exported site is static files, so hosting is free or close to it on the usual providers, and the domain is the only recurring cost — ten to fifteen dollars a year against eighteen a month.
What is the one thing that does not survive the rebuild?
Publishing. Unicorn Platform gets a page live on a domain with a certificate in one click, and that is what most of its customers actually buy. Code you own is worth more in principle and less on the afternoon you want the page up.
Related tools
Receipt