Fields are fundamental for managing structured data within Acquia Source. They serve as core components that specify the type of information stored and the method of input. They allow for the customization of data within each bundle to meet specific requirements.

While Experience Builder handles the visual aspects of page construction, fields provide the structured data necessary for omnichannel content delivery. By defining data types such as text, numbers, or images, fields establish a clear framework for data entry, which ensures consistency and accuracy. This structured methodology enables consistent utilization of content across various channels and experiences.

The following is a sample hierarchical representation of fields:

│
├── Entity Type: Content
│   ├── (bundle) Content Type: Article
│   │   ├── Field: Title
│   │   └── Field: Body
│   └── (bundle) Content Type: Person
│       ├── Field: Name
│       └── Field: Portrait
│
├── Entity Type: Taxonomy
│   └── (bundle) Vocabulary: Tags
│       └── Field: Name
│
└── Entity Type: Media
    └── (bundle) Media Type: Document
        ├── Field: Name
        └── Field: File
    └── (bundle) Media Type: Video
        ├── Field: Name
        └── Field: File

The following field types are available:

• Text fields: Store single-line text with a 255-character limit.
• Text areas: Allow multiline text with formatting and larger character limits.
• Numeric fields: Accept only numbers for items such as product IDs.
• Date fields: Help you to select dates from a calendar.
• Select fields: Provide controlled vocabulary options where you choose from predefined values.
• Multiselect fields: Provide options where you choose multiple values from predefined values.
• Email fields: Validate email address formats.
• URL fields: Validate URL formats.

Each field:

• Stores a specific type of data, such as text, numbers, dates, or files.
• Has configurable settings that control its behavior.
• Can be displayed in different ways depending on context and channel.
• Can be required or optional.
• Can allow single or multiple values.