Custom hook implementations, Ctools plugins, or simply no extensibility at all. We’ve all faced the challenges that needed to be overcome in order to make Drupal modules extensible by others. Drupal 8 introduces the plugin system: a unified approach to discover and instantiate plugins, with a variety of options to customize your own plugin type using different discovery methods and plugin features. By attending this session, you will learn about: * How Drupal core and contributed modules use the plugin system * The available plugin discovery methods * Plugin instantiation * The available features plugin types can provide out of the box * How to write your own plugin types

1. THE DRUPAL 8 PLUGIN
SYSTEM: EXTENSIBILITY FOR
ALL
I am , , and .Xano @BartFeenstra http://mynameisbart.com

2. WHAT ARE PLUGINS?
Swappable extensions that provide logic for a specific (set of) task(s)
Uniquely identifiable
Metadata
Multiple instances can co-exist (reuse)

3. DRUPAL 7 PLUGINS
Hook discovery (core and most contributed modules)
File-based discovery (ctools)
Magic hooks/callbacks/includes
Some plugins are classed

4. SAY WHAT?

5. DRUPAL 8 PLUGINS
Are classed. Always.
Should implement interfaces.
Consistent API for discovering and instantiating plugins, regardless of
type.

6. NO MORE DARK MAGIC

7. JARGON, DO YOU SPEAK IT?

8. PLUGIN TYPE

9. PLUGIN (DEFINITION)

10. PLUGIN DISCOVERY

11. PLUGIN FACTORY

12. PLUGIN MANAGER
(DISCOVERY + FACTORY + ...)

13. PLUGIN INSTANCE

14. PLUGIN CONFIGURATION

15. RECREATING/CLONING
PLUGIN INSTANCES
Using Plugin type/manager, ID, and configuration through
ConfigurablePluginInterface.

16. DISCOVERY METHODS
Annotated class discovery (mostly different logic)
YAML discovery (mostly reused logic)
Static discovery (testing)
Hook discovery (deprecated)

17. ANNOTATED CLASS
DISCOVERY
<?php
/**
* The plugin that handles Data response callbacks for REST resources.
*
* @ingroup views_display_plugins
*
* @ViewsDisplay(
* id = "rest_export",
* title = @Translation("REST export"),
* help = @Translation("Create a REST export resource."),
* uses_route = TRUE,
* admin = @Translation("REST export"),
* returns_response = TRUE
* )
*/
class RestExport extends PathPluginBase implements ResponseDisplayPluginInterface {
// Class contents here...
}
?>

18. YAML DISCOVERY
system.admin:
title: Administration
route_name: system.admin
weight: 9
menu_name: admin
system.admin_content:
title: Content
description: 'Find and manage content.'
route_name: system.admin_content
parent: system.admin
weight: -10
system.admin_structure:
route_name: system.admin_structure
parent: system.admin
description: 'Administer blocks, content types, menus, etc.'
title: Structure
weight: -8

19. FORMS

20. DERIVATIVES
One base plugin definition can be dynamically expanded into multiple
derivative plugin definitions.

21. THERE'S A MODULE FOR
THAT
http://drupal.org/project/plugin

22. PLUGIN TYPE DISCOVERY

23. ADMINISTRATIVE OVERVIEW

24. CONFIGURATION SCHEMAS
plugin.plugin_configuration.*.*

25. TYPED PLUGIN DEFINITION
API
Now: PluginDefinitionMapperInterface
Future: PluginDefinitionInterface

26. PLUGIN SELECTORS

27. FIELD
TYPES/WIDGETS/FORMATTER
S

28. CONCLUSION
EXTENDING DRUPAL HAS NEVER BEEN EASIER.
Review this presentation at .http://slideshare.net/bartfeenstra
Find the Plugin module at .http://drupal.org/project/plugin
I am , , and .Xano @BartFeenstra http://mynameisbart.com
DO YOU HAVE ANY QUESTIONS?
© subsetsum @ Flickr (CC BY-NC-ND 2.0)