webCOMAND

Model

A content model maps out how content is organized in a Base.  It outlines the data, relationships, requirements and customization options of each type of content in your project.

Whether you're working on a straightforward project or creating something entirely novel, models adapt to your needs.  Use pre-built content types, customize them, or build something completely new.

Content Types

Each content item in a Base is associated with a content type, which breaks content into well-defined elements that are easier for teams and apps to work with.

Fields

Fields define the data and relationships of a content type.

  • Data - Numbers, dates, times, text, images, files and more.  These are the smallest "atoms" of content, which are associated with a title, description and restrictions, such as minimum and maximum allowed values and file sizes.
  • Relationships - Connections to other content embedded within or linked to elsewhere.  These connections form a valuable web of content through well-defined relationships.

Methods

Methods determine how a type of content will look and behave when users and apps work with it.  For example, methods determine how content is represented with icons and text, validated upon submission and update, and matched with keyword searches.

Inheritance

A key feature to help define and work with similar types of content is inheritance.  Inheritance makes it possible for content types to be based on another, automatically assuming it's fields and methods.  This simple feature is extremely valuable in many situations.

The best way to get started building a model for your project is with the Bases App.