Perffection

Development preview

What you keep

Keep the work. Keep your options.

Your business should not disappear inside a website builder. Keep a readable copy of your page content and choose what you publish. A complete, independently hostable handover is the standard we are working toward, not a feature we claim to have finished.

What the handoff contains

Six parts another builder can pick up.

A finished handover should include enough context for another builder to take over. These are the parts we keep separate in our own source; the customer export currently contains the saved page document, not this entire stack.

One site, six handover parts, drawn as a stack 01 02 03 04 05 06
The site drawn as a handover stack: six distinct parts, each able to be inspected and carried with the rest.
  1. 01

    The pages

    editable page files, not a proprietary canvas

    The page structure lives in readable files. They are turned into a finished page before publication, so a visitor receives a complete document while a future maintainer still receives the source.

  2. 02

    The words

    kept apart from the layout

    The copy is kept separately from the page structure, so a change to hours or prices can be read and approved without redesigning the page around it.

  3. 03

    The look

    one named design file per page

    Each page receives one finished design file built from a short, ordered set of readable sources. A future maintainer can trace where every choice came from.

  4. 04

    The pictures

    sized files, served from your address

    The images chosen for a page are sized for that page and served from the same address. No image feed or outside content service has to stay alive.

  5. 05

    The lettering

    five licensed faces in this preview

    The typefaces travel with their open licences; you licence them rather than own them. This preview carries five, while a customer site needs only the faces chosen for it.

  6. 06

    The approved versions

    kept whole rather than overwritten

    The current publication history lets you restore earlier page content. A complete release handover must also retain the matching renderer, styles, and other assets; the local content-restoration checks do not prove that wider guarantee.

What does not become your chore

Fewer things to babysit after launch.

Every extra service is another account, bill, outage, or quiet change. This preview leaves out the usual baggage and names the boundary instead of hiding it.

  1. Tracking added by default

    Cannot run

    No script is permitted to execute on this site — not analytics, not a chat bubble, and not something a plugin quietly added. The visitor's browser receives the rule that refuses it.

  2. Fonts borrowed from another company

    Not used

    The licensed typefaces are served with the site, so a page does not report each visit to a font service.

  3. A stack of plugins

    Not used

    The pages, styles, lettering, and pictures travel with the site itself. There is no plugin system waiting for a maintenance round.

  4. A form with nowhere honest to send it

    Not built

    If a customer site later collects something, where it goes, who may use it, and how long it stays need to be built and stated deliberately first.

  5. Stock imagery fetched at page load

    Not used

    The selected pictures are sized for the page and served from the site's own address.

  6. Silent overnight changes

    By approval

    Saving a draft is separate from approving its publication. Template and platform updates still need their own review; content history alone is not a guarantee that software never changes.

Count it yourself

A few things you can verify without asking us.

These figures describe this development preview. Publication checks keep the file count and the page's allowed actions tied to the version that is actually served.

0 scripts
On all three public pages. The browser is instructed to refuse any script rather than relying on our intentions.
1 design file per page
One finished design file for each page, built from an explicit ordered source list.
5 typefaces
Five openly licensed variable faces, all served from this site. A customer page needs only the ones selected for it.
18 site files, each named
The build compares this count with the reviewed list, so the number cannot drift away from the assets that actually ship.
9 design directions
Three invented businesses with three genuinely different directions each, all switched locally in the browser.

The handover standard

Keep your content. Know the boundaries.

You can copy a saved page document from the workspace. The local journey also exercises publishing, republishing, and restoring its content. The site still runs on Cairn, and a complete export of its renderer and assets is not available yet. We will not call a content download a finished website handover.

See the design bench See what backs the promises