[[views-parts]]

=== Concept: The Parts of a View

[role="summary"]
Overview of the administrative parts of a view.

(((View,parts of)))
(((Display part of view,overview)))
(((Format part of view,overview)))
(((Fields part of view,overview)))
(((Filter criteria part of view,overview)))
(((Sort criteria part of view,overview)))
(((Contextual filters part of view,overview)))
(((Relationships part of view,overview)))
(((View,display part)))
(((View,format part)))
(((View,fields part)))
(((View,filter criteria part)))
(((View,sort criteria part)))
(((View,contextual filters part)))
(((View,relationships part)))

==== Was man wissen sollte

* <<planning-data-types>>
* <<planning-modular>>
* <<views-concept>>
* <<content-paths>>
* <<block-concept>>

==== What are the parts of a view?

When you are editing a view in the administrative interface, you will see the
following parts (or Abschnitte), which allow you to specify what data to output,
in what order, and in what format:

Display::
  Each view can have one or more displays, each of which produces one type of
  output. Options for display types include:
  Page;;
    Makes output at a particular URL, for the main page content at that URL.
  Block;;
    Makes output in a block, which can be placed on pages.
  Feed;;
    Makes an RSS or another type of feed.
  Attachment;;
    Makes output that you can attach to another display.
Format::
  Depending on the display type, you can choose to output your data in a
  table, grid, HTML list, or another format. Some formats also give you a
  second choice that lets you output either rendered entities or fields; other
  formats do not give you this choice (for example, if you use a table format,
  you must always use fields).
Fields::
  Depending on the format choice, you may be able to choose which content fields
  are output. For example, if you were making a view of recipe content items, in
  a block display you might show only the recipe names, while in a full page
  display you might also show an image field because you have more space.
Filter criteria::
  Filters limit the data to be output, based on criteria such as whether the
  content has been published or not, the type of content, or a field value.
  For instance, to make a view of recipe content items, you would need to filter
  to the Recipe content type, and to published recipes. Filters can also be
   _exposed_, which means that users will have a form where they can choose
  their own filter values. You might use this on a Recipe page to let users
  filter for recipes with certain ingredients.
Sort criteria::
  Defines the order to present the output, which can be based on any content
  field.
Contextual filters::
  Contextual filters are like regular filters, except that the values come from
  the _context_ of the view display, such as the full URL of the page being
  displayed, the current date or time, or some other value that can be
  detected by the view calculation.
Relationships::
  Relationships allow you to expand what is displayed in your view, by relating
  the base content being displayed to other content entities. Relationships are
  created using fields on the base content that relate it to the other content;
  one example is that all regular content items have an author field, which
  references the user account of the person who authored the content. Once you
  have created a relationship, you can display fields from the referenced
  entity in the view.

==== Ähnliche Themen

<<views-create>>

//==== Additional resources


*Attributions*

Written and edited by https://www.drupal.org/u/surendramohan[Surendra Mohan]
and https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon].
