Layout System
Copy MarkdownAurora UIX provides a flexible layout DSL for organizing fields in index, form, and show views.
The layout system gives you full control over UI structure. By default, Aurora UIX generates layouts automatically from your resource metadata, so you get a functional interface with no extra code. When you need custom arrangements, use the provided DSL to create anything from simple field groupings to complex, tabbed forms with nested sections—all with concise, readable code.
Core Concepts
Layout Types
Each layout type determines how your resource's fields are presented:
index_columns— Selects which fields appear in the list (table) view and their order. Takes a list of field names.edit_layout— Controls how fields are arranged when creating or editing a resource. Renders input fields with metadata options likeplaceholderandrequired.show_layout— Specifies read-only detail view layout using the same resource metadata but rendered as static values.
Sub-Layout Containers
Sub-layouts are organizational containers that structure how fields are displayed. You can nest them freely to achieve complex layouts:
inline(fields)— Arranges fields/sub-layouts horizontally in a single rowstacked(fields)— Arranges fields/sub-layouts vertically in a column (default when no layout defined)group(title, fields)orgroup(title, do_block)— Visually groups related fields under a title with a border/framesections(do_block)— Creates a tabbed container; use withsectionblockssection(title, fields)orsection(title, do_block)— Represents a single tab; holds fields or nested layouts
Field Options
Field-level customizations (like readonly, hidden, renderer) defined in your resource metadata are automatically applied wherever the field appears, across all layouts.
Layout Examples
All examples below use this resource metadata:
auix_resource_metadata :product, context: MyApp.Inventory, schema: Product do
field :reference, required: true
field :name, required: true
field :description
field :price, precision: 12, scale: 2
field :quantity_initial
field :quantity_entries
field :quantity_exits
field :quantity_at_hand
end1. Default Layout (No Configuration)
When you don't define a layout, Aurora UIX automatically generates one from all available fields:
auix_create_ui do
# No layout specified - Aurora generates defaults for index, show, and edit
endGenerated layouts:
- Index: Shows all fields in table columns

- Show / Edit: Displays fields in vertical (stacked) order


2. Inline Layout — Horizontal Field Arrangement
Use inline to display fields side-by-side in a row:
edit_layout :product_location do
inline [:reference, :name, :type]
endResult: Three fields displayed horizontally in a single row.

3. Stacked Layout — Vertical Field Arrangement
Use stacked to display fields one below another:
edit_layout :product do
stacked([
:reference,
:name,
:description,
:quantity_initial,
:product_location_id,
:product_location
])
endResult: Fields are displayed vertically in a column.

4. Group Layout — Bordered Field Grouping
Use group(title) to visually frame related fields under a title:
edit_layout :product do
group "Product Info" do
stacked [:reference, :name, :description]
end
endAlternatively, pass fields directly without a do block:
edit_layout :product do
group "Product Info", [:reference, :name, :description]
endFor example:
edit_layout :product, [] do
inline([:reference, :name, :description])
group "Quantities" do
inline([:quantity_at_hand, :quantity_initial])
end
group "Sale Prices" do
stacked([:list_price, :rrp])
end
end
Result: Fields grouped in a bordered section with a title.

5. Sections Layout — Tabbed Interface
Use sections with section blocks to create a tabbed interface:
auix_create_ui do
edit_layout :product, [] do
inline([:reference, :name, :description])
# section_index_1
sections do
# section_index_1, tab_index_1
section "Quantities" do
inline([:quantity_at_hand, :quantity_initial])
end
# section_index_1, tab_index_2
section "Sale Prices" do
stacked([:list_price, :rrp])
end
end
end
endResult: Multiple tabs; clicking a tab shows only that section's fields.


6. Complex Nested Layout
Combine all layout types for sophisticated UIs:
auix_create_ui do
edit_layout :product, [] do
# sections_index_1
sections do
# sections_index_1 tab_index_1
section "References" do
inline([:reference, :name])
# sections_index_2
sections do
# sections_index_2 tab_index_1
section "Descriptions" do
inline([:description, :status])
end
# sections_index_2 tab_index_2
section "Specifications" do
stacked do
inline([:width, :height, :length])
inline([:weight])
end
end
end
end
# sections_index_1 tab_index_2
section "Information" do
# sections_index_3
sections do
# sections_index_3 tab_index_1
section "Quantities" do
inline([:quantity_at_hand, :quantity_initial])
end
# sections_index_3 tab_index_2
section "Sale Prices", default: true do
stacked([:list_price, :rrp])
end
end
end
end
end
end
Result:
- Top section: Reference and name in the same row
- Middle: Nested section inside the first tab containing description and quantities
- Information tab: Nested section inside the information top level tab containing price related fields



Layout Customization
Layout Options by Type
Each layout type (:index, :form, :show) supports specific customization options that control titles, subtitles, pagination, and more.
Index Layout Options
Controls list view pagination, titles, and row/header actions:
index_columns :product, [:reference, :name, :price],
page_title: "Products",
page_subtitle: "Manage your inventory",
pagination_items_per_page: 20,
pagination_disabled?: false,
order_by: [{:name, :asc}],
where: dynamic([p], p.active == true)Options:
:page_title— Main title (default:"Listing {title}"):page_subtitle— Subtitle (default: empty):pagination_items_per_page— Rows per page (default: 40):pagination_disabled?— Disable pagination (default:false):order_by— Initial sort order; usesAurora.Ctx.QueryBuildersyntax:where— Query filter; usesAurora.Ctx.QueryBuildersyntax
Form Layout Options
Controls edit/new form titles and subtitles:
edit_layout :product,
edit_title: "Edit Product",
edit_subtitle: "Update product details",
new_title: "Create New Product",
new_subtitle: "Add a product to your inventory"
do
stacked [:reference, :name, :description]
endOptions:
:edit_title— Title for edit form (default:"Edit {name}"):edit_subtitle— Subtitle for edit form (default:"Use this form to manage <strong>{title}</strong> records in your database"):new_title— Title for create form (default:"New {name}"):new_subtitle— Subtitle for create form (default:"Creates a new <strong>{name}</strong> record in your database")
Show Layout Options
Controls detail view titles and subtitles:
show_layout :product,
page_title: "Product Details",
page_subtitle: "Full product information"
do
stacked [:reference, :name, :description, :price]
endOptions:
:page_title— Main title (default:"{name}"- the resource name):page_subtitle— Subtitle (default:"Details")
Dynamic Titles & Subtitles
For dynamic content, pass function references (named functions only, not anonymous):
defmodule MyAppWeb.ProductViews do
def custom_edit_title(assigns) do
~H"Edit #{assigns.auix.name} (ID: #{assigns.entity.id})"
end
def custom_page_title(assigns) do
~H"Product: #{assigns.entity.name}"
end
# Layout definitions
edit_layout :product, edit_title: &custom_edit_title/1 do
stacked [:reference, :name, :description]
end
show_layout :product, page_title: &custom_page_title/1 do
stacked [:reference, :name, :price]
end
endThe function receives assigns and should return rendered HTML (using sigil ~H).
Field-Level Options
Customize individual fields within any layout using keyword options:
edit_layout :product do
inline [
reference: [readonly: true, length: 20],
name: [placeholder: "Product name", length: 100],
id: [hidden: true]
]
endRelevant Field Options:
:readonly— Make field read-only:hidden— Hide field from UI:renderer— Custom rendering function:length— Input field character width:placeholder— Placeholder text:option_label— For select/radio fields
Note: Some field options are resolved from the field's
datamap and must be set inauix_resource_metadatarather than inline in a layout (layouts do not accept these rendering options in this version). The:expandedoption forembeds_manyfields is one such case — see the Resource Metadata guide.
For complete field attributes reference, see the Aurora.Uix.Field module documentation.
Actions: Customizing Buttons & Links
Aurora UIX provides a comprehensive action system for customizing the buttons and links rendered in headers, footers, rows, and selection bars of every layout type.
The full reference — action groups per layout type, the
add_/insert_/replace_/remove_operations, default action names you can target, and therow_infointernals — lives in the dedicated Custom Actions guide.
The worked examples below show actions being customized inside layout definitions.
Example: Customizing Index Actions
defmodule MyAppWeb.ProductViews do
use Aurora.Uix.View
# Custom archive action for table rows
def archive_action(assigns) do
~H"""
<.link
phx-click={JS.push("archive", value: %{id: row_info_id(@auix)})}
name={"auix-archive-#{@auix.module}"}
data-confirm="Archive this product?"
>
<.icon class="auix-icon-size-5 auix-icon-warning" name="hero-archive-box" />
</.link>
"""
end
# Custom export action for header
def export_action(assigns) do
~H"""
<.button phx-click="export-all" name={"auix-export-#{@auix.module}"}>
<.icon name="hero-arrow-down-tray" class="auix-icon-size-4" />
Export CSV
</.button>
"""
end
# Custom edit with different styling
def custom_edit_action(assigns) do
~H"""
<.auix_link
class="auix-index-row-action auix-custom-edit"
patch={"/#{@auix.uri_path}/#{row_info_id(@auix)}/edit"}
name={"auix-edit-#{@auix.module}"}
>
<.icon class="auix-icon-size-5 auix-icon-primary" name="hero-pencil" />
</.auix_link>
"""
end
index_columns :product, [:reference, :name, :price, :stock],
# Add custom actions
add_row_action: {:archive, &archive_action/1},
add_header_action: {:export, &export_action/1},
# Replace default actions
replace_row_action: {:default_row_edit, &custom_edit_action/1},
# Remove unwanted actions
remove_row_action: :default_row_show
# Helper to extract row ID from auix context
defp row_info_id(%{row_info: {_index, row_entity}, primary_key: primary_key}) do
Aurora.Uix.Templates.Basic.Helpers.primary_key_value(row_entity, primary_key)
end
endExample: Customizing Form Actions
defmodule MyAppWeb.ProductViews do
use Aurora.Uix.View
def save_and_continue_action(assigns) do
~H"""
<.button
phx-click="save-continue"
phx-disable-with="Saving..."
name={"auix-save-continue-#{@auix.module}"}
>
Save and Continue
</.button>
"""
end
def cancel_action(assigns) do
~H"""
<.auix_back class="auix-button--alt">
Cancel
</.auix_back>
"""
end
edit_layout :product,
add_footer_action: {:save_continue, &save_and_continue_action/1},
add_footer_action: {:cancel, &cancel_action/1}
do
stacked [:reference, :name, :description, :price]
end
endExample: Customizing Show Actions
defmodule MyAppWeb.ProductViews do
use Aurora.Uix.View
def duplicate_action(assigns) do
~H"""
<.auix_link
patch={"/#{@auix.uri_path}/new?duplicate_from=#{@auix.entity.id}"}
name={"auix-duplicate-#{@auix.module}"}
>
<.button class="auix-button--alt">Duplicate Product</.button>
</.auix_link>
"""
end
def print_action(assigns) do
~H"""
<.button phx-click="print" phx-value-id={@auix.entity.id} class="auix-button--alt">
<.icon name="hero-printer" /> Print
</.button>
"""
end
show_layout :product,
add_header_action: {:duplicate, &duplicate_action/1},
add_header_action: {:print, &print_action/1}
do
stacked [:reference, :name, :description, :price]
end
endGoing further
For the action function signature, the assigns available inside an action (@auix, row_info),
primary-key helpers, styling conventions, and how actions are processed under the hood, see
Custom Actions.
Advanced Patterns
Nesting Fields and Blocks
Layouts can accept either a list of fields or a do block containing nested layouts:
# Direct field list
inline [:reference, :name]
# Nested block with sub-layouts
inline do
group "Section 1", [:reference, :name]
group "Section 2", [:description]
end
# Mixed: both fields and nested blocks are allowed
stacked do
inline [:reference, :name]
group "Details" do
stacked [:description, :price]
end
endQueryBuilder for Advanced Filtering
Aurora UIX index layouts support advanced filtering and sorting. The :where and :order_by options are passed to Aurora.Ctx.QueryBuilder.options/2 for query construction.
Basic Filtering with Tuples:
index_columns :product, [:reference, :name, :price],
where: [{:active, true}],
order_by: [asc: :name, desc: :created_at]Using Comparison Operators:
The :where option accepts tuples with operators for complex filtering:
index_columns :product, [:reference, :name, :price],
where: [
{:price, :greater_than, 10},
{:name, :ilike, "%widget%"}
],
order_by: :nameSupported Comparison Operators:
:greater_thanor:gt- Greater than:greater_equal_thanor:ge- Greater than or equal:less_thanor:lt- Less than:less_equal_thanor:le- Less than or equal:equal_toor:eq- Equal to:like- Pattern matching (SQL LIKE with%and_):ilike- Case-insensitive pattern matching:between- Range query (requires start and end values)
Range Filtering with Between:
index_columns :product, [:reference, :name, :price],
where: [{:reference, :between, "A", "M"}],
order_by: :referenceMultiple Sort Fields:
index_columns :product, [:reference, :name, :price],
order_by: [asc: :category, desc: :price, asc: :name]This enables:
- Complex filtering with comparison operators
- Multi-field sorting with customizable directions
- Pattern matching with LIKE/ILIKE operators
- Range queries with BETWEEN operator
Conditional Field Visibility
Use field options to hide fields conditionally:
edit_layout :product do
stacked [
id: [hidden: true], # Always hidden
reference: [readonly: true], # Visible but read-only
name: [] # Normal editable field
]
endBest Practices
- Keep layouts readable — Avoid deeply nested structures; prefer multiple groups over excessive nesting
- Use meaningful group titles — Titles help users understand field organization
- Group related fields — Use
grouporsectionsto organize logically related fields - Test responsiveness — Layouts adjust for mobile/tablet; test on multiple screen sizes
- Leverage sections for long forms — Use tabs to avoid overwhelming users with too many fields at once
- Keep field order consistent — Match order between index, edit, and show layouts when possible
- Use field options judiciously — Overriding too many field options makes maintenance harder; prefer metadata-level configuration
Related guides
- Customizing & Extending Aurora UIX — the central customization hub
- Resource Metadata — field configuration options
- Custom Actions — the full action system reference
- LiveView Integration — handle custom events in your layouts
- Styling Aurora UIX in a Host Application — styling generated layouts
- Troubleshooting — common layout issues