Drafts and version history for pages

This is a written-up look back at 10 to 23 May 2026, published on 12 October 2026. Period covered: 10-23 May 2026. The lead feature of these two weeks is Save versus Publish, with drafts and version history for store pages.

In short

• Saving a page and publishing it became two different actions, with named drafts, version history and restore.
• We built landing-page features: hide the header and footer, give a page its own domain, add a floating call-to-action bar.
• Reviews, marketing consent, analytics tags, AI search-engine text and a three-plan structure also landed on staging.

Lead feature: Save is not Publish

Until early May, saving a page in our editor could put the change in front of buyers straight away. That is fine for a typo and bad for a half-finished page the night before a camp registration opens.

The fix was a versioned model for pages, built over 21 and 22 May:

• Working copy and published version. Each page has a draft you edit and a published version that buyers see. Save writes the draft only. Publish promotes the draft in one step.
• An "unpublished changes" dot on the Publish button. It tells you the live page is behind your draft.
• Version history with restore. Each publish becomes a numbered snapshot you can open and bring back.
• Named drafts. You can keep more than one draft of a page, give each a name and switch between them. Each draft has its own undo history, saved with it.
• Conflict protection. If two people or two tabs edit the same page, the editor stops the second save with a clear message instead of silently overwriting the first.

Older pages were given a first draft and a first snapshot automatically, so nothing was blank after the change. Pages that had no draft yet kept the old behaviour until they got one, so no page could paint empty.

What else we built

Landing pages. A page can now be a landing page.

• Hide the site header and footer on that page.
• Point a separate domain at one page, so `promo.yourbrand.com` opens that page directly.
• Set analytics tags for just that page.
• Pin a floating call-to-action bar to the edge of the screen.
• Send people to a thank-you address after a form is submitted.

Reviews, second version. A buyer can leave a review from a link in an email, without logging in, and add photos. A review request email can go out after an order. Buyers have a "My Reviews" tab, and product pages show reviews automatically.

Marketing consent. Newsletter and buyer signups now record whether the person agreed to marketing email. The customer list shows a consent column you can filter on, and the customer page shows the status. Every marketing email carries an unsubscribe link that the platform enforces.

Analytics tags. Google Analytics 4, Google Tag Manager and the Meta Pixel can be switched on from the integrations settings and are added to the storefront.

AI search text. An AI writer drafts search-engine titles and descriptions per page and for the homepage. There is a new SEO page in the storefront section and an "AI & SEO" tab on products.

Domains and email. Domains were split from email. The system checks DNS records automatically and supports sending store email from your own domain.

Plans. The plan structure became three tiers: Starter, Pro and Scale. The pricing page and the plan cards read what each plan includes from one source. For what each costs and includes, see pricing.

Billing page. Rebuilt with clearer buttons, real usage meters and fixed invoices.

Subscriptions and funnels. A subscriptions workspace for creators, and funnel definitions with recovery actions per step.

Pie. Pie gained more tools for orders, support tickets, inventory, reviews, notifications and the link-in-bio page. It can also remember facts you tell it.

Settings. The sidebar was simplified: rarely-used settings moved into a single settings hub with a short hint on each tile.

What it means for a coach or academy

Draft and publish is the change a small team will feel most. A coach can prepare next season's registration page, keep it as a draft, and publish when ready. A mistake in a published page can be rolled back from history.

Landing pages fit a camp, a challenge or a trial class: one page, its own address, no site menu to distract a visitor. Reviews with photos by link suit a studio whose students are not going to create an account.

The consent tools matter if you email parents. You can see who agreed to marketing, and every marketing email has an unsubscribe link. That does not make you compliant by itself; it gives you the records.

What is next

The next fortnight, 24 May to 6 June, is where the buyer started getting offers in the cart. Support tools, segments and email templates came with it. The next post is about that. You can also see the AI course generator and the BioLink page.

Want to talk? I am one of the co-founders of PersonaCart. If you have a question, an idea or something you want us to build, write to me directly: [email protected].

Vinod Morya, Co-founder, PersonaCart