Articles

Cache contexts = (request) contextual dependencies

Cache contexts are similar to the HTTP Vary header.

Why?

Cache contexts provide a way to create context-dependent variants of something that needs to be cached. It makes caching logic easier to read and avoids repeating the same conditional logic wherever context-based variation is needed.

Examples:

Cache max-age = time-based dependencies

Cache max-age is similar to the HTTP max-age directive in the Cache-Control header.

Why?

Cache max-age provides a declarative way to create time-based cache dependencies.

Varnish Cache is a web application accelerator, also known as a caching HTTP reverse proxy. Varnish is used on thousands of Drupal sites to increase page load performance by 10-1000x, and it can be used with cache tags to simplify cache invalidation.

For basic cache tag integration, you need to do three things to ensure Varnish works well with the cache tags generated by Drupal:

The CacheableDependencyInterface in Drupal 8 simplifies working with cache tags, cache contexts, and max-age.

This interface operates at the intersection of the Cache API and Response. Since it is primarily a response, this is where the core information resides.

See also

• CacheableResponseInterface
• Responses in Drupal 8
• Cache API in Drupal 8

Route access checkers, hook_entity_access(), and anything that is expected to return an AccessResultInterface object must add appropriate cacheability metadata.

If you haven’t yet, read about cache tags, cache contexts, and max-age.

The CKEditor API is new in Drupal 8.

Note that this only applies to the CKEditor module API in Drupal 8, not the CKEditor JavaScript library API – for that, see http://docs.ckeditor.com/.

For more detailed information about what this module does, see the Text Editor module documentation.

API Features

Organized by least commonly used APIs:

CKEditor Skins

Drupal Configuration API.

The Configuration API provides a central place for modules to store configuration data. This data can be simple configuration, such as your site name, or more complex information managed via configuration entities, such as views and content types.

Configuration is the place to store information that you want to synchronize from development to production. This information is often created during site building and typically not generated by regular users during normal site operation.

Drupal 8 includes several types of information:

• Content

Information intended for display on your site and editable by users: articles, basic pages, images, files, etc.

• Session

Information about individual user interactions with the site, such as their current filter selection in views. This is ephemeral and personalized to one user.