Skip to content

Instantly share code, notes, and snippets.

@alexpott
Last active May 25, 2022 14:05
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save alexpott/2accc39d1da28a5049f977d2e864a588 to your computer and use it in GitHub Desktop.
Save alexpott/2accc39d1da28a5049f977d2e864a588 to your computer and use it in GitHub Desktop.
Example starter template
# Example starter template based on the discussions in https://docs.google.com/document/d/1_PoxyIPND-d2TkgrThzivcJS8B_Bg1gIIrkFsGDtmCM
name: 'An example starter template'
description: 'A description of the functionality'
# The type key is similar to the package key in module.info.yml. It
# can be used by the UI to group starter templates. Additionally,
# the type 'Site' means that the starter template will be listed in
# the installer.
type: 'Content type'
apply_first:
# Other starter templates that should be applied prior to this
# starter template.
- editorial_ui_for_publishers
suggests:
# Other starter templates that once this starter template has been
# applied should be suggested to the user.
- moderated_content_for_publishers
composer:
require:
# An array of things to pass to composer require.
- 'drupal/easy_breadcrumb:^2.0.1'
install:
# An array of modules or themes to install, if they are not already.
# The system will detect if it is a theme or a module. During the
# install only simple configuration from the new modules is created.
# This allows the starter template control over the configuration.
- easy_breadcrumb
- node
- text
config:
# A starter template can have a config directory. All configuration
# is this directory will be imported after the modules have been
# installed.
# Additionally the starter template can install configuration entities
# provided by the modules it configures. This allows them to not have
# to maintain or copy this configuration. Note the examples below are
# fictitious.
import:
easy_breadcrumb:
- views.view.easy_breadcrumbs
node:
- node.type.article
# Configuration actions may be defined. The structure here should be
# entity_type.ID.action. Below the user role entity type with an ID of
# editor is having the permissions added. The permissions key will be
# mapped to the \Drupal\user\Entity\Role::grantPermission() method.
actions:
role:
editor:
permissions:
- 'delete any article content'
- 'edit any article content'
content:
# A starter template can have a content directory. All content in this
# directory will be created after the configuration has been installed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment