Custom Objects Became a Native Content Surface
Teams can model structured records for custom datasets like sponsors, venues, and membership tiers that don't fit default collections.
Sponsors, memberships, and venue resources never quite fit the default page, event, person, or post collections. Basker now has a richer custom object model for partner and organisation-specific data, so teams can model structured records that do not fit those defaults.
What you can model
Sponsors, schools, membership tiers, venue resources, artist rosters, campaign assets, and other custom datasets can become part of the CMS instead of living in spreadsheets or external databases.
For partners
Partner workflows can provision custom object structures more consistently, making them a practical tool for organisation-specific publishing rather than a developer workaround for each new customer.