Drafts, Autosave, And Version History For Every Content Type

You can now edit any content in Basker without worrying about pushing half-finished changes onto your public site. Working drafts, autosave, and version history used to apply only to pages and posts. They now cover every content type, so your whole team can revise, review, and refine before anything goes live.

Every collection, not just pages

Drafts and version history now extend across blogs, venues, works, series, organizations, people, seasons, and individual event instances, alongside pages and posts. Wherever you manage content in Basker, you get the same safe editing model: your edits are saved as a draft, and the published site keeps showing the last version you approved. An event instance follows its parent event, so a draft performance stays hidden until that event is published, and ticketing sync keeps on-sale and availability current on both your published page and your open draft without overwriting your editorial edits.

Edit safely while you work

As you make changes, Basker autosaves your work as a draft in the background. Nothing you type appears on the live site until you publish, so there is no risk of visitors seeing an unfinished record. When you are ready, publishing promotes your draft, and the version history keeps a record of what changed.

Check and share before you publish

Each record now has its own view-live and share-preview buttons. View-live takes you straight to the published version so you can compare. Share-preview gives you a link to the work-in-progress draft, so a colleague or stakeholder can sign off before you make it public.