๐ 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,364 โฆ ๐ tell a friend โฆ best viewed in Ruby on Rails โฆ ๐ click here to see what’s new โฆ
Dynamic Collections
coming soonBuild collections that assemble themselves from live queries. No manual curation required.
# $30/mo
gem "avo-dynamic_collections"
Spin up a brand-new Avo resource from inside the app, no model, migration, or code deploy. Add a record in the Collections menu and Dynamic Collections defines the model, the Avo resource, and the controller for you at runtime, then reloads the routes so the new resource appears in the menu with full CRUD a moment later.
Every collection's records live in one shared entries table (title, slug, and
a JSON data column), and each entry carries an avo-meta panel so you can attach
custom meta fields without a schema change. Rename a collection and the menu
entry swaps cleanly; remove it and its resource and routes disappear. The setup
survives boot and code reloads, so what your team builds in the UI stays put.
That is a whole admin-authoring layer you would otherwise design, build, and
babysit yourself.
See it in action
What you get
- Create and manage collections from a Collections menu entry, no code
- Each collection becomes a live Avo resource, model, controller, and routes defined at runtime
- Full CRUD on the new resource the moment it is created, no app restart
-
Entries stored in one shared table with
title,slug, and a JSONdatacolumn -
Per-entry meta fields through
avo-meta, no migration to add them - Rename or delete a collection and its menu entry, resource, and routes update cleanly
Why it pays off
- Let your team stand up a new resource in the UI this afternoon instead of writing a model, migration, resource, and controller for every one.
- Defining constants, reloading routes, and surviving code reloads without leaks is fiddly metaprogramming. We carry that, you do not.
- It is a gem you add, not a runtime-resource engine your team builds, documents, and keeps working as Avo and Rails move.
- Bugs in the dynamic-define and teardown path are in our back yard, so we fix them once for everyone.
# included in
(no bundles)