Use case
A landing page for a software product
A headline, the three things the product does, a pricing table and a form. A landing page is a conventional shape, and a conventional codebase is the right thing to hand a developer afterwards.
What you might ask for
A landing page for a cybersecurity SaaS with pricing, FAQ and a contact form.
A landing page for an invoicing tool, with a pricing table and a sign-up form.
What vibld produces
- A landing page with the sections you asked for, in React and TypeScript, with shadcn/ui components to hand for things like an FAQ accordion and the form.
- Motion for the entrances, from the Motion library, with a reduced-motion rule the design checks look for.
- A project a developer can push to GitHub as a pull request and review like any other change.
Worth knowing first
- The sign-up form needs an endpoint of yours to post to. Until it has one, the page says the form is a demonstration.
- Prices, plan names and claims about your product are whatever you put in the request. Check them before you publish.
Then the same flow as everything else: a staged checkpoint to read, a private preview, and export, a pull request or a publish when you are ready. How it works
A real one
Built by vibld from the prompt shown, with no hand edits. Each has a live copy and its source on the examples page.
A cybersecurity SaaS
A landing page for a cybersecurity SaaS with pricing, FAQ and a contact form