Default theme implementation for a generic views UI container/wrapper. Available variables: attributes: HTML attributes to apply to the container element. children: The remaining elements such as dropbuttons and tabs. File core/modules/views_ui/templates/views-ui-container.html.twig Related topics Theme system overview Functions and templates for the user interface that themes can override.

Default theme implementation for a views mini-pager. Available variables: items: List of pager items. See also template_preprocess_views_mini_pager() File core/modules/views/templates/views-mini-pager.html.twig Related topics Theme system overview Functions and templates for the user interface that themes can override.

Default theme implementation of a views exposed form. Available variables: form: A render element representing the form. See also template_preprocess_views_exposed_form() File core/modules/views/templates/views-exposed-form.html.twig Related topics Theme system overview Functions and templates for the user interface that themes can override.

Default theme implementation for each "box" on the display query edit screen. Available variables: attributes: HTML attributes to apply to the container element. actions: Action links such as "Add", "And/Or, Rearrange" for the content. title: The title of the bucket, e.g. "Fields", "Filter Criteria", etc. content: Content items such as fields or settings in this container. name: The name of the bucket, e.g. "Fields", "Filter Criteria", etc. overridden: A boolean indicating the setting has

Default theme implementation for Views UI display tab settings. Template for each row inside the "boxes" on the display query edit screen. Available variables: attributes: HTML attributes such as class for the container. description: The description or label for this setting. settings_links: A list of links for this setting. defaulted: A boolean indicating the setting is in its default state. overridden: A boolean indicating the setting has been overridden from the default. See also tem

Overview of the Views module API The Views module is a generalized query and display engine, which can be used to make views (formatted lists, grids, feeds, and other output) of items (often entities, but can be other types of data). Developers can interact with Views in several ways: Provide plugins: Views plugins govern nearly every aspect of views, including querying (sorting, filtering, etc.) and display (at several levels of granularity, ranging from the entire view to the details of a fi

Static service container wrapper for views. Hierarchy class \Drupal\views\Views File core/modules/views/src/Views.php, line 8 Namespace Drupal\views Members Name Modifiers Type Description Views::$handlerTypes protected static property A static cache for handler types data. Views::$plugins protected static property A list of all available views plugin types. Views::$translationManager protected static property The translation manager. Views::analyzer

Describes various views templates & overriding options. All views templates can be overridden with a variety of names, using the view, the display ID of the view, the display type of the view, or some combination thereof. For each view, there will be a minimum of two templates used. The first is used for all views: views-view.html.twig. The second template is determined by the style selected for the view. Note that certain aspects of the view can also change which style is used; for example

Hooks that allow other modules to implement the Views API. Parent topics Views overview Overview of the Views module API File core/modules/views/views.api.php, line 72 Describes hooks and plugins provided by the Views module.

Defines a page controller to execute and render a view. Hierarchy class \Drupal\views\Routing\ViewPageController File core/modules/views/src/Routing/ViewPageController.php, line 11 Namespace Drupal\views\Routing Members Name Modifiers Type Description ViewPageController::handle public function Handler a response for a given view and display.