Custom Controls

See it in action

What it looks like

Each bar is a block on the resource. Compose built-in buttons, your own links, and Avo actions, and reach for default_controls when you only want to add to Avo's defaults rather than replace them.

Docs for each bar: Show, Edit, Index, and Row.

# app/avo/resources/post.rb
class Avo::Resources::Post < Avo::BaseResource
  # Show: built-ins plus a custom link and an action, shown conditionally
  self.show_controls = -> do
    back_button label: ""
    link_to "View on site", post_path(record), target: :_blank
    action Avo::Actions::Publish, style: :primary unless record.published?
    delete_button
    edit_button
  end

  # Edit: keep Avo's defaults, add one button of your own
  self.edit_controls = -> do
    link_to "Preview", preview_post_path(record), target: :_blank
    default_controls
  end

  # Index: group links into a dropdown, then the create button
  self.index_controls = -> do
    list label: "Export", icon: "heroicons/outline/arrow-down-tray" do
      link_to "CSV", export_posts_path(format: :csv)
      action Avo::Actions::EmailReport
    end
    create_button label: "New post"
  end

  # Row: per-record buttons, hidden in grid view
  self.row_controls = -> do
    action Avo::Actions::Feature, label: "Feature", style: :primary unless params[:view_type] == "grid"
    show_button
    edit_button
    delete_button
  end
end

What you get

• Separate control bars for Show, Edit, Index, and table-row views via show_controls, edit_controls, index_controls, and row_controls
• Built-in buttons to compose: back_button, edit_button, delete_button, save_button, create_button, detach_button, and attach_button
• Add your own link_to links, trigger Avo actions, and group items into dropdown lists with dividers
• Per-control label, title, icon (Heroicons), style (:primary, :outline, :text), and color
• Plain Ruby conditionals to show or hide a control based on the record
• default_controls to drop Avo's standard buttons back in alongside your custom ones

Why it pays off

• Rearranging a control bar with a custom button takes a few lines in the resource this afternoon, not a custom view layer you spec and build over a sprint.
• Every Avo release makes it better: the control bars on Show, Edit, Index, and row views keep working through upgrades, without you re-patching overridden templates.
• The DSL covers Show, Edit, Index, and row contexts across many apps, so it handles authorization and per-view differences a one-off override tends to skip.
• One less piece of admin UI for your team to own, document, and support.