Websites and CMS

Tedix CMS uses Emdash for website content and Astro themes. A human or agent can inspect a site’s collections, create a draft, revise it, and publish it. Theme editing and deployment are separate from everyday content publishing. For Git-backed product documentation, use Documentation sites.

Availability

CMS is part of the invited Cloud beta. Start with an organization that already has a provisioned site and an authorized CMS connection. If Sites is empty, ask your Tedix beta contact to provision the site and connect its authoring app; site registration currently requires a platform operator. Signing in alone does not create a website.

The root local launcher does not provide a ready-to-use CMS trial. Starting a CMS Worker locally does not provision its tenant, content collections, theme bundle, or authenticated authoring connection. Own-account CMS installation remains experimental operator work.

Publish one small item

1. Confirm the intended organization with tedix -w acme auth status, replacing acme with your workspace. Use the agent guide to discover its CMS tools and request the exact input schemas. Namespace names depend on the connected site; do not copy another organization’s namespace.
2. Read get_site_overview, then schema_get_collection for the collection you want to use. Follow its actual fields and types rather than assuming every site has a posts collection.
3. Use content_create to create a small draft. Read it back with content_get and review the title, body, slug, and intended destination with the human.
4. When publication is authorized, call content_publish for that exact item. Open its canonical public URL and verify the rendered content. A successful draft save is not evidence that the item is publicly visible.

This editorial loop does not require a Worker deployment. If a tool is absent or access is denied, report the missing connection or permission rather than guessing a callable or switching organizations.

For source work, start with apps/cms (authoring and theme builds) and apps/cms-runtime (serving tenant sites). Read their scoped guides before editing.