Definitions and other various terms that are exclusive to the Directus Ecosystem.
An external application using Database managed data.
An API install managing one or more projects on a server.
A database, config, and file storage directory. Also used for deployment environments (eg: prod, stage, dev).
A flag set in the project config: either production or staging (not to be confused with deployment environments).
The SQL database's architecture, not including any content.
The base schema and system content included in a fresh/blank copy of Directus.
A set of items, saved as a SQL table
A single record of data. Contains values for the fields. Saved as a SQL row.
A single piece of information contained in an item. Saved as a SQL column or alias.
A field that does not actually map to a database column (eg: a divider or the one side of a relationship).
The SQL vendor-specific database storage type (eg: VARCHAR, BIGINT, etc)
An extended and agnostic storage type mapped to SQL vendor datatypes (eg: string, number, etc). Also includes non-DB style types that provide extra functionality into the system (eg m2o, translation, etc).
The amount/size of data that can be stored in a single field.
The GUI for a field (the actual thing that the user interacts with to create and edit the data for the field).
The GUI for a collection's items. Displays the items in the user-set way.
Anything that extends the core codebase, including: Interfaces, Pages, Storage Adapters, SSO Services, etc.
Descriptive text displayed with a field.
A Mustache-style string used to format field values (eg: {{first_name}} {{last_name}}, {{title}})