SITEHOME
Docs menuEditing and publishing

Using SiteHome

Editing and publishing

Concepts, review, new items, taking an item off the website and history.

Fields

Open a content group, then an item. SiteHome shows the fields it can edit in a form made for a phone: text, long text with headings and lists, images, dates, choices, yes/no, lists of items and galleries, depending on what the website has. Required fields, lengths and link rules come from the website's own CMS.

Fields SiteHome leaves alone are listed under Niet te bewerken in SiteHome (Not editable in SiteHome), each with a plain reason, and a button opens the item in the CMS's own editor. How SiteHome decides.

Concepts

Bewaar concept (Save concept) keeps your changes in SiteHome; nothing is written to the website. Open concepts are listed in the Recent tab. When you resume one, SiteHome reads the item again first; if someone changed it in the meantime, you review again.

Review

Bekijk wijzigingen (Review changes) shows every change word by word, with the website it will be published to. You can go back and adjust, or publish.

Publish

Publishing is an explicit tap, and only when publishing is switched on for the website. SiteHome reads the item again right before it writes; if anyone changed it after your review, it stops and asks you to review again. On Sanity, SiteHome publishes through a draft with revision checks; on WordPress, the SiteHome plugin checks the revision again on the website itself. Official Payload MCP uses final schema/source/draft checks and confirms stored values and publication status after writing, but has no atomic revision guard: a simultaneous change between the final check and write can still be overwritten.

New items

In a content group, add a new item, such as a blog post or a project. SiteHome gives it its own address from the title. A new item is reviewed and published like any other change.

Taking an item off the website

Van website halen (Take off website) takes a published item off the website without deleting it: it stays in the CMS as a draft and can be published again.

History

Every publication is listed per day with what changed, who did it, where it went and whether it came from the AI assistant. Terugzetten (Restore) puts a previous version back through a normal reviewed publication.

Markdown for AI assistants