Autom8ion

Capability

This page is a content entry. That is the demonstration.

Everything you are reading was authored as blocks in the platform's own content management, published to its own edge, and themed by its own accessibility system. We did not build a sales site and then describe the product; we put the sales site on the product.

A closed vocabulary, for the same reason the email designer has one.

Accessibility decided before the first byte.

The reader's choice of look is applied on the server from a cookie, so the page arrives already in the right theme rather than flickering into it after a script runs. The choice is device-local on purpose: most visitors are not a person the site knows yet, and asking somebody to have an account before they can read comfortably is the wrong way round.

The options include higher contrast, larger text, colour-blind-safe palettes and reduced motion, plus Follow my system for anyone who has already told their operating system what they need.

  • Applied server-side on the first response, not after hydration
  • Device-local, so it works for a visitor with no record
  • Follow my system honours the setting the reader already made
  • The same token set the rest of the platform themes from

Written for machines as well as people.

Pages are emitted as lean markup rather than a framework's debris, because a crawler — and increasingly an agent answering a question on somebody's behalf — reads what is actually in the response. Structured data is published as JSON-LD where it genuinely describes the page rather than sprayed across every template.

Search-engine fields are part of the page record rather than a plug-in: title, description, canonical, share image, and an index or no-index switch that means what it says.

  • Lean markup, no decorative wrapper elements
  • JSON-LD where it describes something real
  • Canonical, share image and no-index on the page record itself
  • Redirects managed in the product, with import, export and an undo

Questions about content

Can I have my own content types?

Yes. Define the type and its fields, then create entries against it through the screens or the API. Website pages and site settings are platform-owned so the rendering contract holds, but your own types sit alongside them and behave the same way.

Why is there no free HTML block?

Because the moment there is one, every security property of the page becomes a review process instead of a guarantee. The block list is closed for the same reason the email designer's is: a vocabulary that cannot express a script tag does not need to be policed for script tags.

What stops a broken link reaching the site?

Publishing checks them. A page linking to something unpublished is refused with the specific links named, so the failure happens to an author rather than to a visitor.

Who can publish?

Publishing is a separate capability from authoring, so you can have people who write and people who release. Four-eyes review can be required per site, and every publish is audited like any other action.

Can we run more than one site?

Yes — sites are per tenancy with their own settings, navigation, domain and theme. This one is a tenancy of the same platform, which is the shortest honest answer we can give about whether it works.

The quickest way to judge a content model is to try to express a page you already have in it. Bring an awkward one.

Bring a page you cannot build today.

Book a demo