Possibilities & boundaries

Small beginnings.
Room to grow.

Improbable Publishing is a flow for creating durable, versioned websites through conversation, with little to no web development knowledge required.

01

A timely little website

An event, a workshop, or a temporary project. Give people one clear place to find what they need.

02

A lasting resource

A guide, a project home, or a collection of public information that grows as your work does.

03

An interactive experience

A calculator, an explainer, or a React interface. Static hosting can still support useful interaction in the browser.

Thoughtful by design

Useful, accessible,
and good to look at.

The flow is designed to keep accessibility and aesthetics in view: clear structure, readable colors, keyboard access, and layouts that work across screen sizes.

Those are goals to check throughout a project. A generated draft still needs review, including its content, interactions, and accessibility.

A history you can return to

Website source is stored in GitHub with version history. That makes it possible to understand changes and recover earlier source versions. Returning to an earlier live version requires publishing that source again.

Connecting the pieces

Your site can be
part of something bigger.

When you need a backend

The platform hosts static website files; it doesn’t include a built-in database or application backend. A site can connect to other services for capabilities that need them. Suitability, access, and data handling need to be worked through for each project.

Ask Rhett about backend integrations before planning around one.

A different address may be possible

Sites normally publish at a subdomain of pub.improbable.site. A different address, such as a subdomain of education.uci.edu, may be possible with administrator coordination.

This is an option to discuss with Rhett, rather than a self-service setting.

Want to see what’s underneath?

Follow the publishing flow →