Expanded Custom Attributes Across Content Model

Adding a new field for every launch used to mean a schema change. Custom attributes now extend to event instances, organisation-level settings, posts, and more field configurations, so teams can add structured metadata without treating every launch as a schema change.

Why this matters for event teams

Attributes are now genuinely useful for access notes, genres, age guidance, sponsor flags, availability labels, booking exceptions, and internal reporting fields. These values can appear on public themes or partner APIs without a developer needing to add a new field each time.

What is now covered

Event instances, posts, organisation settings, and additional field configurations are all included in this expansion. The attribute model is consistent across the content types that matter most for cultural organisations.