Create artifacts
Publish a page, files or a filled template and get a private link.
guide~2 minVerified v0.71.0
You'll have a private link to the page your agent publishes.
Publish this
The agent publishes what you made and returns its private link.
What the agent sends
super_publish takes a complete page as html, with small assets in files, or a template with its filled values. Larger files are staged with super_upload and included through uploads; valuesFile can name staged JSON values.
A policy declares what visitor input the page may store. Without one, it stores no visitor input. visibility: "private" keeps the page private from its first version; leaving visibility out uses the workspace default.
This is a super_publish call for one page:
{
"slug": "weekly-update",
"title": "Weekly update",
"prompt": "A short status update for this week",
"html": "<!doctype html><html lang='en'><title>Weekly update</title><h1>Weekly update</h1><p>Ready for review.</p></html>",
"kind": "page",
"visibility": "private"
}
slug is its stable name; prompt records why it was made; html is the page itself. The reply includes the artifact and its live link.
Seven kinds
| Kind | What a visitor does |
|---|---|
| page | Read |
| slideshow | Advance through |
| survey | Answer |
| tracker | Add entries to |
| video | Watch |
| tool | Operate |
| dashboard | Watch numbers move |
The kind describes what people do with the artifact: read a page, advance a slideshow, answer a survey, add to a tracker, watch a video, operate a tool, or follow a dashboard.
Versions keep the link
Publishing the same slug saves a new version and moves the live link to it. Earlier versions stay available; restoring moves that pointer back. Versions and publishing explains the model.
Check it worked
The returned link opens your page, and its Versions tab lists the publish.
Next: Get feedback.