Site content API

Same push model as the blog publishing API: your site exposes a small manage API and stays the single source of truth. Trakys proxies the editor's calls with the key you saved — it caches nothing and never talks to your database directly. The capability set is deliberately narrow: create, update and hide. There is no delete endpoint anywhere in the chain — hiding is the one way off the public site, and nothing is ever lost remotely.

All routes live under /v1/manage and are guarded by a bearer API key with content scopes (content:read, content:write, content:hide):

Authorization: Bearer spk_your_management_key

GET    /v1/manage/{collection}            list items
POST   /v1/manage/{collection}            create an item
PATCH  /v1/manage/{collection}/{id}       update an item (partial)
POST   /v1/manage/{collection}/{id}/hide  {"hidden": true | false}

Collections the editor renders today: projects, technologies, texts. Your API's error statuses (400, 404, 409, 422, 429) pass through to the editor with their messages; a 401/403 from your site is reported as “the site rejected the management key” — never confused with a Trakys session problem.

1. Implement the manage API on your site (Spine-based sites get it from the platform; anything that speaks the routes above works).
2. In Trakys, open the site's Connection tab → Content management and paste the API URL and the management key. The key is stored encrypted and shown only as a ••••hint afterwards; replacing it needs project owner/admin rights.
3. The Content tab is now the editor — list, create, edit and hide items collection by collection.