This one embeds a View inside a page as a paragraph — and the first thing to know is which kind of View display the field will accept.
Block displays only
The reference field is configured with its plugin types limited to block. Page displays, feed displays and the default display are all switched off. So before you reach for this bundle, open your View and confirm it has a Block display; if it only has a Page, the autocomplete will not find it. That single setting explains most of the "my View is not in the list" confusion around this bundle.
What the bundle contains
Two content fields: a Content Title, and the View reference itself, edited with an autocomplete widget supplied by the contributed Views Reference module, which the sub-module declares as a dependency. No preselected views are enabled in the shipped configuration, so every block display on the site is available to pick from.
Why put a View in a paragraph
Placing a view block through the block layout ties it to a region and a set of visibility conditions. As a paragraph it becomes part of the content: an editor can position it between two other paragraphs, reorder it, and give it the bundle's own background colour, opacity, width, padding, border and shadow from the Display tab — all without touching site configuration.
The W3CSS Paragraphs module page covers the rest of the suite.
Core support
Drupal 10, 11 and 12 are all accepted, with PHP 8.1 or newer. The Paragraphs Bundles successor requires Drupal 11.3 at minimum, so on older cores this remains the way to embed a view in content.
Need this built into your own site? See Drupal development services, or request a quote.
