Use cases
Eight kinds of website,one set of tools.
A campaign page and a shop catalogue look nothing alike from the outside. Inside castomUI they are made of the same parts: pages of blocks, components behind the blocks, a template around them, data where there is data, and a publisher at the end. What changes is which of those parts carries the weight.
The pages below are not eight products. They are eight routes through one editor, each written for somebody who already knows what they are building and wants to see which windows they will actually spend their week in. If your site is not on the list, ask which of these it resembles most: one page or fifty, written by hand or drawn from a database, one language or several, new or inherited.
Landing pages
One page, one campaign, one deadline. Generated from a prompt, arranged as blocks, shared with the client on a hidden preview and published to cstmui.com the same afternoon.
See how it worksCompany websites
A dozen pages, a header and footer that never drift, menus, a contact page, a 404 and redirects — on your own domain, with SEO handled per page rather than remembered at launch.
See how it worksPremium websites
Your own components in your own HTML, CSS and JavaScript, custom fonts and animation, minified or obfuscated output, pushed to GitHub and reviewed by the team with notes.
See how it worksOnline stores
The storefront side of a shop: a catalogue in datasets or read from your existing shop database, one page per product, product OpenGraph. Checkout stays in the shop system you connect.
See how it worksPresentations
A website that behaves like a deck: full-screen sections as blocks, a link instead of an attachment, one clone per audience, installable and readable offline.
See how it worksPortfolios
A studio's work shown one project to a page: the layout built once as a component, the projects kept as records, the pictures in the media library, and a case study that can sit finished as a draft until the client's own launch.
See how it worksMultilingual websites
Language set per page, block and menu. Clone and translate with DeepL or an LLM, keep interface strings in dictionaries, and publish one language to one target when that is what you need.
See how it worksRebuilding a website
Crawl the old site, scrape and analyse what is there, prepare the pages, generate a new project from the source URL, and keep every old address alive with 301 redirects.
See how it worksDifferent desks,
the same windows open on every screen.
How the toolkit changes shape.
Components and templates are the constant. On a landing page you barely touch them; on a premium site they are most of the work, written in code and kept for the next project.
Datasets are optional until they are not. A company website may never open that window; a store lives in it, because a dataset page turns one template page into one page per product.
AI generation does the first draft of almost anything — a project, a sitemap, a page, a block, META — and the difference between site types is mostly how much of that draft survives. Publishing is the last step in all seven, and the target is what varies: cstmui.com, your domain, GitHub, or a custom publisher.
- 1Landing pageAI generation, blocks, switchers, preview code.
- 2Company websiteTemplate, menus, META for all pages, own domain.
- 3Premium websiteComponent code, base CSS, output switches, GitHub.
- 4Online storeDatasets, external sources, dataset pages, media.
- 5PresentationFull-screen blocks, clones, Web App Manifest.
- 6MultilingualClone and translate, dictionaries, per-language menus.
- 7RebuildWeb crawler, scrape and analyse, redirects, web checker.
- ·Same editorEvery one of them is windows beside a live preview.
One accountOne editor
Which plan,
roughly.
Landing pages, company websites, presentations and most multilingual sites fit Regular at €100 a month: the whole builder, AI, SEO, translation and publishing to cstmui.com or your domain. Stores and rebuilds usually need PRO at €300, because datasets, external sources, the web crawler and GitHub publishing live there. Premium work done by more than one person is what Team, at €500 a seat, is for. There is no free tier; pricing has the detail.
A small warning: most projects turn out to be two of these at once. The company website grows a shop, the landing page grows a second language, and the rebuild was always going to be a premium website in disguise.
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