The Views component embeds a Drupal View — a dynamic list of content built by your site administrator, such as “latest news” or “upcoming events” — inside a Page Builder page. The list updates itself as content is published. You can show the View exactly as designed, or reshape its results into a grid of boxed cards.

What it is for

Whenever a page should contain content that lives elsewhere and changes over time: news teasers on a landing page, the next three events beside an intro text, a table of documents filtered by category. The other components hold content you type in; Views pulls content in automatically.

See it live on the example page APB Views, which embeds a table View as is and the same View as boxed cards.

Structure

This component has no items of its own: its content is the result of the selected View. It has three parts:

• The View field — which View and which of its displays to embed, plus a few overrides (title, header, items per page, offset, pager, argument).
• The Display type — View as Is or Boxed Card.
• The usual shared settings (title, intro, width, placement, container).

Component settings

Setting	Options	Default	What it does
View	a View + display	— (required)	Pick the View from the list, then its display (for example Block or Default). The View overrides below appear after choosing.
Section title / Display Section title / Intro Text	—	— / No / empty	See Section Title and Intro Text.
Target placement	Body, Main Content Top/Bottom, Top region, Sidebars, Internal Placement 1–3	Body	See Target Placement.
Display type	View as Is, Boxed Card	View as Is	View as Is renders the View with its own style (table, list, grid…) untouched. Boxed Card takes each result row and shows it as a card in an APB grid; it requires the View display to use the Unformatted list or HTML list style.
Number of columns	1 … 10	1	Boxed Card only. See Columns and Column Gap.
Column Gap	0 … 60px	20px	Boxed Card only; ignored with one column.
Boxed Card Border Settings	width per side, color, padding	none	Boxed Card only: border width for top/right/bottom/left, border color, and the padding applied on the sides that have a border.
Component width	25% … 100%	100%	See Component Width.
Custom class	text	empty	See Advanced settings.
Container Settings	—	32px bottom margin	See Container Settings.

The columns, gap and border fields are shown in the editor only while Boxed Card is selected.

View overrides

Under the View selector you can adjust, without editing the View itself:

Override	What it does
Include View Title	Shows the View’s own title above the results (in addition to, or instead of, the Section title).
Hide header	Removes the View’s header area (for example a result counter or an intro).
Items per page	How many results to show (leave empty to keep the View’s setting).
Offset	Skip the first N results — useful to show items 2–4 when item 1 is featured elsewhere.
Pager	None, or the View’s pager (mini or full) when there are more results than shown.
Argument	A value passed to the View’s contextual filter, for example a category ID, so the same View can list different things on different pages.

How to use it

1. Ask your administrator which Views are available for embedding (they must be published Views with a suitable display).
2. Click Add Views; choose the View and display.
3. Keep View as Is when the View already looks right; switch to Boxed Card to lay the results out as cards, then set columns, gap and borders.
4. Adjust the overrides (items per page, pager, title/header) and save.
5. Check the page. If Boxed Card shows an error, the View display uses a style it cannot split into rows — switch back to View as Is or ask for an unformatted display.

Tips

• In View as Is, the APB columns and gap do not apply; the View’s own style decides the layout.
• Pager links reload the page; place a paged View where the reload is not disruptive (not inside a Tabs panel).
• Combine with a Section title and Container Settings to give the embedded list the same look as the other components on the page.

For site builders

Item	Value
Module	apb_pb_views (lifecycle: experimental)
Paragraph type	apb_pb_views (no item bundle)
Requires	apbuilder, Paragraphs, Entity Reference Revisions, Field Group, Views Reference (viewsreference ^2.0), core Views / Taxonomy / Text
Own config	vocabulary apb_tax_vw_display_type (view_as_is, boxed_card); fields field_apb_vw_view (viewsreference), field_apb_vw_display_type_tx, field_apb_vw_boxed_border (JSON via the apb_views_boxed_border widget)
Shared vocabularies	apb_tax_columns, apb_tax_column_gap, apb_tax_width, apb_tax_target_placement
Rendering	ViewsRowBuilder executes the View at render time: View as Is uses buildRenderable(); Boxed Card themes each result row as apb_vw_item. Border CSS is scoped inline; output is cached per content language. Editor JS (form_admin) toggles the Boxed Card fields.
Known caveat	On viewsreference beta installs the schema must be at 8103 (apb_pb_views_update_10003 handles it) to avoid failing legacy updates.
Container settings	Full profile.
Example page	/apbuilder_examples/apb-views (source rows: content type apb_views_example)