Publishing
Built in one place,published wherever it needs to live.
A castomUI site can go out to castomUI hosting on *.cstmui.com, to your own domain, into a GitHub repository, or to any number of custom targets you define. Publish one page or the whole project, decide how the output code is shaped, and share an unpublished site with a code instead of a password.
Four destinations
Pick the one that fits,
or use several.
castomUI hosting
Publish to an address on *.cstmui.com and the site is live. Nothing to configure, which makes it the natural home for a first version, a campaign page or a site under review.
Your domain
Publish to your default connected domain, so the site answers at the address on your business card rather than ours.
GitHub
Push a page or the whole project into a repository. The output becomes files in version control, where your own deployment pipeline, reviews and history already live.
Custom publishers
Named targets of your own: a URL, a secret code shared only with that target, and an optional limit to a single language. Each shows its last deployment time, publishes on demand and can be cloned.
Custom publishers,
one per job.
A custom publisher is the answer to "our site does not live in one place". The Polish version goes to one server and the German version to another; a staging copy goes somewhere only the team can see; a client's infrastructure receives the files it expects.
Because each publisher carries its own output switches, the staging target can keep readable code while the production target is minified and obfuscated. Clone a publisher when a new target is mostly like an existing one, and change the one line that differs.
The last deployment time on each is the quiet feature: it answers "is this the version that is live?" without anybody opening a terminal.
- 1Production · PLLanguage: Polish only · Minify · Obfuscation · Service worker
- 2Production · DELanguage: German only · Cloned from Production · PL
- 3StagingAll languages · Readable output · Secret code set
- !DraftsSkipped by every publisher, whatever the switches say
Invented targets and timesEach publisher has its own switches
This page,
or the whole project.
Every destination offers the same choice. Publish this page when you have corrected a price or a phone number and the rest of the site should stay exactly as it was. Publish the whole project when a change runs through the template, the menus or many pages at once.
A page marked draft is not publishable until the mark is removed. That is the rule, not a default: a half-written page cannot go out by accident because someone published the project for an unrelated reason. When a publish finishes, the result is a list linking every page that went out, so checking the work is a matter of clicking down it.
One button between the editor and the world.
Several, if you need them.
Output switches
Decide what the published code is like.
Minify
Smaller HTML, CSS and JavaScript on the wire. Nothing changes on screen except how quickly it arrives.
Prefetch
Subpages load on hover, ahead of the click, so moving through the site feels immediate.
Obfuscation
Source code obfuscation for the work you would rather not hand over with every page view.
Service worker
Fast repeat visits, and a site that copes when the connection does not.
Static handler
A switch for how the published site is served, available on the project and on each custom publisher.
Read-only mode
A project-level switch in the advanced settings, alongside multilingual, for a project that should be looked at rather than changed.
Show it before it is public.
Every project has a preview code. Give it to a client, a manager or a translator and they see the hidden preview of the site without it being published and without an account of their own.
It replaces the usual ritual of a password-protected staging server, a forwarded screenshot and a PDF of the homepage that was out of date by the time it was opened.
A tested observation: the fastest way to find a typo on a homepage remains publishing it. The preview code exists so that the person who finds it is on your side.
- 1DraftVisible in the editor · never published
- 2Preview codeVisible to whoever has the code · not public
- 3PublishedLive at cstmui.com, your domain, GitHub or a custom target
- ✓Result listLinks every page that went out
The three states a page can be inUnmark draft to publish
Questions
The ones people ask before going live.
Am I tied to castomUI hosting?
No. Your domain, a GitHub repository and custom publishers are all first-class destinations, and one project can use several of them.
Can one language go to a different server?
Yes. A custom publisher can be limited to a single language, so each language version can be published to its own target.
Does publishing one page republish the site?
No. "This page" publishes that page only; "whole project" publishes everything that is not a draft.
Where do I check what went live?
The result list after each publish links every published page, and each custom publisher shows its last deployment time.
Every window,
one website.
Open the editor and arrange them the way the job needs.
Open castomUI See pricing