Define fields & connections

After creating a collection, the next step is to define its schema – the fields that each item in the collection will have. By customizing fields, you structure the content for all items. For example, a "Case Study" collection might have fields for Client Name, Project Description, Logo Image, etc. This guide shows how to add and manage fields in a collection.

Managing the Schema

Navigate to your collection in the Collections panel and select the collection you want to configure. Look for an option or icon to manage fields (it might be labeled Schema, Fields, or a gear ⚙️ icon next to the collection name). Click this to open the Field Schema Manager. A panel will appear showing the current fields of the collection and options to add new ones.

Default Fields

Every collection starts with some system fields:

Name: The title or primary identifier for the item (required). Often used as the page title.
Slug: The URL segment for the item's page, usually derived from Name.

You might also see default SEO fields (e.g., SEO Title, SEO Description) depending on Pixelesq's defaults. These can be filled per item to optimize search results. Plan your schema around what content you'll need for each item.

Adding Fields to the Schema

Creating a New FieldTo add a custom field, click the Add Field button in the schema manager. Collection schema editor with custom fields.

A new field row will appear:

Enter a Field Label (human-friendly name for the field, like "Author" or "Date")
Choose a Field Type from the dropdown

Field Types AvailablePixelesq provides various field types depending on your needs:

Text Field: For short text
HTML Editor: For rich text content
Media Field: For images or video
Date/Time: For dates
Option: For dropdown lists
Reference: For linking to other collections

Configuring Fields

Each field type has specific settings you can configure:

Required: Mark if the field must be filled
Max Length: Set character limits for text fields
Default Content: Define starting values
Options: For dropdown fields, list choices (e.g., "Startup, Agency, Enterprise"):contentReference[oaicite:4]{index=4} Defining an Option field with a list of choices.
References: Choose target collections for reference fields

Publishing Your Schema

Once you've added and configured all needed fields:

Review all field settings
Click Publish Schema (or Save/ Done)
Pixelesq will update the collection with the new structure

Important: If you already had items in your collection, they'll now have new empty fields to fill in. It's best to finalize your schema before adding many items.

Best Practices

Name fields descriptively but keep labels short
Group similar fields together (e.g., keep all image fields in one section)
Finalize schema before adding many items

Troubleshooting: If you don't see a field type you need, consider if another type can serve the purpose (e.g., use a Text field for a simple URL). Some field types may be added in future updates – contact Pixelesq support if you have a specific need. Also, if a slug or field key shows a warning, it means a similar field name exists; try renaming the field label to resolve conflicts.

Common Issues: