castomUI
Open castomUI

Overview

Everything a website needs,in windows beside the website.

castomUI is one editor with nine parts. Each part opens as a window next to a live preview of the site you are building, so pages, components, data, pictures, SEO, publishing and the conversation about all of it happen in the same place, at the same time, on the same project.

From a name
to a published site.

1 · Start

From a name, a prompt or the address of an existing website.

2 · Structure

A page tree, templates for the shared frame, menus.

3 · Build

Blocks from components; content through forms, design through code.

4 · Feed

Media, datasets, external databases, translations.

5 · Review

Drafts, private previews, notes on elements, the project chat.

6 · Publish

cstmui.com, your domain, GitHub or a custom publisher.

Most website builders are very good at step three and quietly assume the others will sort themselves out. They do not. A real website is a structure that grows, content that several people change, data that lives somewhere else, pictures that need licences and ALT text, an old site whose addresses still get traffic, and a deadline that somebody else set.

So castomUI treats each of those as a first-class part of the editor rather than an add-on found three menus deep. The rest of this section walks through them one at a time; the short version is below.

The nine parts

What each window is for

Pages and blocks

Nested page tree with drag ordering, page details and SEO switches, drafts, template header and footer per page, blocks you move, hide, clone, translate or send to another page, and menus built from a page's anchors in one go.

Components and templates

Components are HTML, CSS and JavaScript with a JSON data structure and default data; templates carry shared blocks, head and body code and the fonts. Clone, lock, or generate either with AI.

AI generation

A project from a prompt or a URL, a sitemap, pages, blocks, components, META tags, llms.txt, base CSS, images and translations — with the context and the model you choose.

Datasets and content

Typed datasets on MongoDB or MySQL, views, relations, pages generated from records, external databases, global variables and multilingual dictionaries.

Media library

Drag-and-drop uploads of images, video, documents and fonts; AI images; five royalty-free stock libraries; ALT, TITLE, tags, EXIF; duplicate removal.

SEO and migration

Web crawler and checker, scrape-analyse-prepare for old pages, META for every page at once, canonical and indexing control, OpenGraph, llms.txt, redirects.

Publishing

This page or the whole project to cstmui.com, your domain, GitHub or custom publishers, with minification, prefetching, obfuscation and a service worker as switches.

Collaboration

Owners, editors and viewers; invitations; notes pinned to elements; project chat; saved window layouts; screen sharing and co-working on Team.

Plugins

Mailing campaigns, an Eclicks PRO connection, a matching system and a member-community moderation console, installed per project.

Every part of a website,
and every part of it open at once.

The project settings
that hold it together.

Underneath the nine parts sits one settings window per project, and it is where the decisions that affect every page live: the project's name and language, which page is the homepage and which is the 404, and the default AI model everything else will use unless told otherwise.

It holds the private description that gives AI the context to write like your company rather than like a brochure, and the public one published as llms.txt for the language models reading your site. It holds favicons, the Web App Manifest that makes the site installable, OpenGraph defaults for sharing, additional code for the head and body, base CSS, global variables and the redirection list.

And it holds the switches: multilingual, read-only, minified output, prefetch on hover, source obfuscation, service worker, static handler. Plus the two things you reach for at the end — clone this project, and delete it.

Start with pages and blocks

Settings · one projectIllustration
  • 1GeneralName, language, homepage, 404 page, preview code, default AI model.
  • 2IconsFavicon .ico 16×16 and .png 64×64.
  • 3DescriptionPrivate context for AI · public text for llms.txt.
  • 4Additional codeHEAD, BODY, CSS, JS — base CSS can be generated.
  • 5AdvancedMultilingual · read-only · minify · prefetch · obfuscation · service worker.
  • 6WebManifest · OpenGraphInstallable name; default share card.
  • +AdditionalsGlobal variables and the redirection list.

Users · Clone · DeleteOne window

Why windows,
and not another sidebar.

Because the job is rarely one thing at a time. Fixing a product page means the page, the block, the component behind it, the dataset record feeding it and the note from the person who spotted the problem. In a sidebar that is five round trips. In castomUI it is five windows, and the preview that shows whether you fixed it.

Windows remember where they were, a layout can be saved and reopened, and the windows manager puts a tidy desk back in one click when the afternoon has made a mess of it.

A confession: everybody opens too many windows on the first day. The windows manager exists because we did too.

Nine windows.
One website.

Open the editor and arrange them the way the job needs.

Open castomUI See pricing

Illustrations by GetIllustrations.com (Ghost pack).