๐ BIG NEWS ๐ โฆ Avo 4 has officially SHIPPED โฆ ๐ the beta is over, 4.0 is here โฆ ๐ ๏ธ build admin panels, dashboards & internal tools at light speed โฆ โญ you are visitor #1,137,389 โฆ ๐ tell a friend โฆ best viewed in Ruby on Rails โฆ ๐ click here to see what’s new โฆ
Meta
coming soonAdd rich metadata and SEO controls to your records without touching your models.
# $20/mo
gem "avo-meta"
Add custom fields to a model without touching a migration or a resource file. Meta lets you define new properties from inside Avo: pick a name and a field type, and they show up on the record's New, Show, and Edit views. It stores everything in a single JSON column on the model, backed by StoreModel, so you get typed attributes without a wide, ever-changing schema.
Include the Avo::Metaable
concern in a model and Meta gives that resource a "Meta Properties" entry in
the sidebar plus a Meta panel in its views. Each property reuses a real Avo
field type, text, number, boolean, date, select, code, and more, and reads
back like an association: @user.meta.shoe_size.
Building a no-code custom-field system on top of Avo means schemas,
StoreModel wiring, type casting, and default backfills you would otherwise
design and own yourself.
See it in action
What you get
- Define new properties from inside Avo: set a name and a field type, no migration or resource edit
- Properties reuse real Avo field types: text, textarea, number, boolean, date, date and time, code, select, and more
- Per-property options for default value, placeholder, help text, required, and which views to hide on
-
Adds a Meta panel to a model's New, Show, and Edit views by including the
Avo::Metaableconcern -
Stores values in one JSON column via StoreModel, read back like an association (
@user.meta.shoe_size) - Changing a property's default backfills existing records through a background job
Why it pays off
- Let non-developers add a custom field in the UI instead of opening a ticket for a migration every time the data model needs to grow.
- Skip the parts that aren't a first draft: the JSON schema, StoreModel wiring, type casting, and default backfills are already built and tested.
- Every Avo release makes it better: it reuses Avo's own field types and keeps working through upgrades, without getting stranded or you patching it.
- One less internal custom-field system for your team to design, document, and support.
# included in
(no bundles)