Talking Drupal #452 - Starshot & Experience Builder

Today we are talking about web design and development, from a
group of people with one thing in common… We love Drupal. This
is episode #452 Starshot & Experience Builder.


For show notes visit:
www.talkingDrupal.com/452
Topics

What is Starshot

What is Experience builder

How will Starshot build on Drupal Core

Will Experience builder be added to Core

Listener thejimbirch:

When will people hear about their pledge



Listener brook_heaton:

Will experience builder be compatible with layout
builder



Will Experience builder allow people to style content

Listener Matthieu Scarset

Who is Starshot trying to compete with



Listener Andy Blum

Does the DA or other major hosting companies plan to
set up cheap, easy hosted Drupal



Listener Ryan Szarma

Who does this initiative serve in the business
community



How can people get involved

Resources

Drupal Starshot

Experience Builder

Guests

Lauri Eskola - lauriii
Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan
John Picozzi - epam.com johnpicozzi
Matthew Grasmick - grasmash
MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu


Brief description:

Have you ever wanted to have your modules create
content when they’re installed? There’s a module for that.



Module name/project name:

Default Content



Brief history

How old: created in Oct 2015 by prolific contributor
Lee Rowlands (larowlan) though the most recent releases are
by Sascha Grossenbacher (Berdir), also a maintainer of many
popular Drupal modules

Versions available: 2.0.0-alpha2, which works with
Drupal 9 and 10



Maintainership

Security coverage: opted in, but needs a stable release

Test coverage

Documentation

Number of open issues: 105 open issues, 29 of which are
bugs against the current branch



Usage stats:

Almost 20,000 sites



Module features and usage

Provides a way for modules to include default content,
in the same way that many modules already include default
configuration

The module exports content as YAML files, and your
module can specify the content that should be exported by
listing the UUIDs in the info.yml file

It also provides a number of drush commands, to export
a single entity, to export an entity and all of its
dependencies, or to bulk export all of the content
referenced in a module’s .info.yml file

There is also a companion project to export default
content using an action within a view, which also makes me
think it could probably be automated with something like
ECA if you needed that

Exported content should be kept in a content directory
in your module, where it will imported during install on
any site that has the default_content module installed

I thought this would be a good module to cover today
because Drupal core’s recipe system also includes support
for default content, so when you install a recipe it will
similarly import any YAML-encoded content in the recipe. In
fact, I used this module for the first time exporting
taxonomy terms I wanted a recipe to create as default
values for a taxonomy it creates. Since Recipes will be a
big part of Starshot, I expect default_content to be
getting a lot of use in the coming months