Building multilingual runtime collections in a Filament plugin

Building multilingual runtime collections in a Filament plugin I just released v1.2.0 of Filament Studio, a Filament v5 plugin I am building for runtime collections, custom fields, dashboards, filters, and APIs. The short version: this release adds multilingual support. The longer version: adding multilingual support to a runtime data model is not the same as adding a translations JSON column and moving on. Filament Studio is built for admin panels where the data model changes after the app is already running. A user can create a collection, add fields, manage records, build dashboards, and expose API endpoints without writing a new migration and Filament resource for each new content type. That flexibility creates a specific problem for translations. If the fields are defined at runtime, translation behavior also has to be defined at runtime. The problem I wanted to solve In real admin systems, multilingual content is rarely all-or-nothing. A collection mi