Landing pages
One page,one campaign,one afternoon.
A landing page has a short life and a hard deadline. It needs to exist by Thursday, be approved by somebody who will not log in to anything, look right when shared, and be cloned for the next campaign without starting again. That is the whole brief, and castomUI is arranged around it.
From prompt to page.
Start a project with AI generation: describe the campaign, paste a source URL if there is an existing site to draw tone and facts from, and pick the model. What comes back is a page made of blocks — hero, benefits, proof, offer, form — each an instance of a component with a settings form generated from its data structure. You edit words and images in the form, not in code.
A block that is close but not right can be changed with AI on its own, with the page and project context you choose. "Generate all the content" runs over every block marked ready, in order, which is the fastest way to turn a structure into a first draft.
Anchors, switchers and a menu
that builds itself.
Give each block an anchor and the menu window's "Add elements" builds a navigation from those anchors in one go. On a single page that is the whole menu.
A switcher is a set of interchangeable blocks in one place: two headlines, three offers, a hero with and without video. Keep the alternatives on the page, flip between them on the preview, and show the client both before anyone decides.
Set the page OpenGraph — title, description, type, image from the media library — so the link looks deliberate when it lands in a message. Then send the preview code: a hidden preview the client can open without the page being public.
- 1HeroSwitcher: two headlines, the client picks one.
- 2BenefitsThree cards, drafted by AI, rewritten by hand.
- 3OfferPrice and dates from a global variable.
- 4FormShort, one field fewer than anybody asked for.
- ·MenuBuilt from the four anchors with "Add elements".
- 5PublishPreview code approved, then published to cstmui.com.
Four blocksOne link to approve
Approved before the office light went off.
After launch
The second campaign costs a fraction of the first.
Publish in minutes
Publish the page or the whole project to cstmui.com, or to your connected domain. The result list links every published page. See publishing.
Clone for the next one
Clone the project with only the homepage, swap the switcher's winner in, and change the offer. The components, template and styles come along.
META without guessing
Title, description and keywords per page, or generated with AI. Covered in SEO and migration.
Which plan
Regular, at €100 a month for one seat, covers all of this: generation, blocks, switchers, media including AI images and stock, OpenGraph and publishing to cstmui.com or your domain. PRO is only worth it if the landing page reads from a dataset. Compare plans.
Questions
Can the client see the page before it is public?
Yes. Set a preview code in project settings and send the link; the page stays hidden from everyone else.
Is a switcher an A/B test?
No. It keeps alternative blocks in one place so you can compare and choose. Splitting traffic and measuring the result is not something castomUI claims to do.
Do I need to write code?
No. Blocks are edited through forms. Code is there if you want it, in components and additional HTML, CSS and JS.
Can I reuse sections on another page?
Yes. Move or clone a block to another page, or into a template so it appears everywhere.
From experience: the headline the client picks from the switcher is rarely the one you liked. Keep both. The next campaign will want the other one.
Your website next.
Start it today.
Open the editor, describe the website, and publish the first version to a cstmui.com address.
Open castomUI See pricing