Post Grid

Create a repeated post layout with preset column or editorial grid arrangements. The Post Grid wrapper controls layout; its nested Column contains the query and the card elements.

Setup and First Use


Before starting, enable the relevant element or feature family under Bricks → BricksUltimate → General Elements, save, and reopen the Bricks editor. Integrations also require their corresponding plugin to be active.

  1. Add (BU)Post Grid and inspect the generated Column child in Structure.
  2. Select the Column, which starts with a posts query, and configure the post type, item count, ordering, and other query settings.
  3. Edit the image and title inside the Column and add excerpts, metadata, or buttons as needed.
  4. On the outer Post Grid, choose Grid layout and Gap.
  5. Set the Tablet, iPad, and Mobile column controls for the desired responsive arrangement.
  6. Test several result counts and long post titles, including an empty query.

Controls and Settings


ControlPurpose and usage
Grid layoutChoose two to six columns or the available Template 1-5 layouts. The Custom option is commented out in the current selector, so do not rely on it being selectable.
GapControls the spacing between repeated grid items.
Columns in BreakpointsThe exposed preset labels refer to Tablet <=991, iPad <=768, and Mobile <=620. Verify them against the rendered layout.
Alignment / Auto-placementUse the available grid alignment and auto-row/column/flow controls without confusing them with data-query settings.
Nested ColumnOwns the query and card contents. The initial query uses posts with 3 items; change that child query for the actual collection.

Wrapper Versus Repeated Item


Keep Post Grid outside the query. Repeating the entire Post Grid produces several grids rather than one collection of cards. The generated child uses grid-item classes; preserve the structure and inspect the effect before replacing it with unrelated markup. Use the query controls on that child, not a second competing query on the wrapper.

Editorial Presets and Pagination


Asymmetric presets depend on item positions, so inspect the last row with fewer results and each responsive breakpoint. Pagination belongs to the query, not the CSS layout; if added, connect it to the repeated child and test actual page changes. A nice-looking three-card preview does not guarantee a ten-page archive behaves correctly.

Practical Example


Build a six-post news grid. Set the nested Column query to six published posts, choose a three-column layout on the wrapper, then use two columns on tablet and one on mobile.

Troubleshooting


  • Same card repeated: check child dynamic fields and fixed content.
  • Only three posts: update the nested query's initial posts-per-page setting.
  • Several separate grids: move the loop back to the repeated child.
  • Unexpected card spans: review preset choice and responsive column settings.

Related Documentation