Content in Sitearc is a set of decisions, not a text editor. Your agent finds the topic and writes the draft. A person approves the brief, the draft and the time it goes out.
Brand and context
Each site has a brand kit: logos, colours, fonts, voice, phrases to use and to
avoid, and business context. Your agent reads it with get_brand_profile.
Your agent can suggest changes with propose_brand_patch or
propose_context_change. A person accepts them. Nothing changes the brand on
its own.
From brief to draft
- Your agent finds a topic in the site’s own data and adds it with
create_content_brief. - You approve the brief in Work › Content. Nothing is written before that.
- Your agent opens the draft with
start_content_draftand writes it. - It saves each version with
revise_content_document, then callssubmit_content_for_approval.
Sitearc does not show article bodies. You read each draft at the preview link your agent supplies.
Approve, or ask for changes
Each piece reads Needs approval, Drafting, In review, Ready to publish or Published. Request changes with a note, and your agent revises.
Approving a draft’s preview approves that exact draft. A changed draft needs a new review.
Publishing
publish_content opens a pull request on your repository. It never puts a
post live. You merge in GitHub.
Your agent can propose a time to publish with schedule_content_publication. A
person approves the schedule.
What is not covered
Publishing to WordPress needs the WordPress plugin, which is not released. Sitearc does not write drafts itself. Your agent does.