Content Schema is the combination of Content Models, Content Fields, and their respective behaviors. Content Schema provides the guidelines for creating, editing, and accessing content in a Zesty.io Content Instance. Changes to Content Schema also shapes the patterns of a Content Instance's auto generated API by assigning unique identifiers.
Content Models contain instructions (options and fields) that determine the format of the content items that can be created and stored in them. For example, let's pretend we created a content model called Person, and Person has two fields: name and date of birth. Person now serves as a model to follow when entering or editing content in the Person content model.
Content Fields are stored on a content model to determine what type of content can be stored. Content fields are created with three key attributes:
Name (A label used to guide people conducting content entry)
Reference Name (used by programmers, only alphanumeric characters and underscores)
Data Type (used to determine input options and data requirements)
Content Fields Names
Date of Birth
Fields can control what type of data is stored, for example, text or number, They also determine what the editing interface for a user is. Fields can be one of many types.
simple text, limit 256 characters
simple text, can contain HTML, 256 characters, produces a larger input area
What You See is What You Get (wysiwyg), is a rich editor that provides t e user with tools to format text with titles, bolding, italics, links, video embeds etc.
A text editing area that supports the markdown format
a numeric character 0-9999999999
a float style number 99.99
a numeric character -9999999 - 9999999
a field that stores an image reference Zesty.io Micro DAM
a field that stores a file reference from Zesty.io Micro DAM
accepts a full URL
accepts a ZUID to a content item
accepts a date in the format YYYY-MM-DD HH:mm:SS
accepts a date in the format YYYY-MM-DD
a boolean field that can have custom labels on a toggle
creates a pre-populated dropdown controlled by the user generated options
One to one relationship to another content model's content item (requires relationship field on creation)
One to many Relationship to another content model's content item. (requires relationship field on creation)