TessryxDocs

Content records

One actual item of data, a JSON document that follows a schema, edited in an auto-generated form.

A content record (its technical name is a datafile) is one actual item of data (this product, that blog post) stored as a JSON document that follows a schema. If the schema is the shape, a content record is one thing of that shape.

You edit records in Content Studio, through the form the schema generates. Records live in folders (really just a prefix on a record's slug), so a site with hundreds of them stays browsable. This is the surface you'll spend the most time in; see Content and editors.

#Draft and published

Every record has two states: the draft you're editing and the published copy. Saving updates the draft; publishing promotes it.

For a content record, "published" has a specific, important meaning: the published copy is served, unauthenticated, from the CDN at a public URL. The draft never is. It's reachable only server-side or in the editor. So publishing a record is the act of making its data public, and the draft/published split lets you prepare a change privately and release it deliberately.

References pin which one they read: @published (the public copy) or @latest (the draft, reachable server-side only), so a page can serve the live data while you stage the next version.

#Reading a record, and the headless-CMS use case

  • Server-side: a workflow is handed the record and builds the page from it (it can read the draft too, for a preview).
  • From anywhere: anything can fetch a published record straight from its public CDN URL. This is what makes Tessryx usable as a headless CMS: you edit in the auto-generated form, and your own frontend (a React or Next app hosted anywhere) pulls the published JSON directly from the CDN. The form is your admin panel; the record's CDN URL is your API. (A workflow-rendered page on Tessryx is just the other option, not a requirement.)

A just-published record can take up to a minute to appear on the CDN: the published copy is briefly cached. See Credits and caching.

#Deleting

Deleting a record is permanent, and anything still reading it (a live page, another workflow) stops resolving. Tessryx warns you before you confirm.