The Website section now shows the site, its leads and its releases

The Website area of a workspace now shows the live site, where its form enquiries went, and every publish as a release you can restore. Underneath, requests from partners became one record with one owner, and our own servers and domains got a real inventory.

Most of today went into the websites we host for clients and into the plumbing behind them. The Website area stopped being a placeholder and became a place you can actually work from.

For our partners

1. The Website page shows the site itself: a live preview, visits over the last thirty days, recent changes, and a button into the editor.
2. Enquiries from a site’s forms reach the people you nominate, with the newest ten listed on the same page.
3. You choose whether changes go live as they are published, or wait on staging until someone presses Publish now.
4. Every publish is recorded as a release, and an older one can be restored: the live pages and the staging content both go back to where they were.
5. A Requests tab takes change requests for a site, and if you connect an assistant to the platform you can now give it the websites and nothing else.

1. What the Website page shows

The preview is the real site, scaled into the page, so you can see what a client sees without leaving the workspace. Beside it sits a day by day strip of visits and a list of the most recent content changes, which answers the two questions that usually start a client call.

2. Where form enquiries go

Recipients are set on the site’s settings as a plain list of addresses, and a new site defaults to the business’s own email. Each enquiry is emailed with reply-to set to the person who sent it, any webhooks you have configured are fired, and the page records whether it reached anyone.

3. Holding a change until someone says yes

Automatic publishing is still the default. On manual, work can pile up on staging and the card tells you how long it has been waiting, then Publish now ships it. Either way, a publish that still carries leftover sample copy from the starting template is refused and the live site is left exactly as it was.

Behind the scenes

1. Anything a partner is waiting on is now one record with an id, one owner who sees it through, and its own to-dos, however it arrived.
2. The agent that reads your notes now keeps what a team member saw on a site as a fact about that site.
3. Our servers, domains and sites are inventoried from the vendor accounts outward rather than from the sites inward.

2. Teaching the note reader what counts

A note about a site’s caching behaviour kept coming in and the agent kept filing nothing. The reason was in our own instructions: one rule said a team member’s write-up only becomes a fact when it echoes the client, another threw out anything that would read the same on every campaign. Between them they discarded the one thing worth keeping. We replayed real notes through the old wording and the new one, including a control we did not want to move, and shipped only once the control held.

3. Starting from the accounts

Every list we had started from the sites and worked backwards to ask who the registrar was, which is how domains go quiet. Now the accounts are the source and our lists are reconciled against them, with each domain’s registry record deciding what is renewed, what is in a grace period with the renewal unpaid, and what has actually dropped. A lapsed name can look healthy on its expiry date alone, so the date is no longer what we trust. Much of the screen work came from table and search parts we had already built for the rest of the platform.