Publish is the outward face. Burton’s end goal is reaching new companies and people — job boards, rental sites, events, and physical mail — without leaving the workspace.

The Agent can draft a site or a posting. You still finalize, then verify the public URL and capture settings.

Sites

Team-owned YAML static sites. Pick a render engine (Zola by default), a template, and a theme. The site itself is schema.org/WebSite. Generated projects are agent-ready (llms.txt, JSON-LD, crawler-friendly robots.txt).

Bundled templates:

TemplateForCapture
Job Posting / Job Applyschema.org JobPosting catalogsApply form POSTs to rabun-forms
Vacation Rental / Inquiryschema.org VacationRentalInquiry form POSTs to rabun-forms

Engine, template, theme, and base URL lock after the first save. Git publishing is built in. Burton never stores the public form token.

This marketing site is a sibling rsites tree, not a Burton Sites render — same Zola idea, different CLI.

Source: src/plugins/sites

Job postings and events

Job Postings and Events are YAML documents you create and then attach to a site. They are how a team shows up in search and on a public board.

Postcards

Physical-style cards to contact addresses and lists, with a scheduled send date. Use them when the reach is postal rather than a site.

Source: src/plugins/postcards

After a capture

Public apply and inquiry POSTs become Burton rows (contacts, resumes, forms). rabun-wiki can materialize them. Follow up from Communicate and Manage.