Talking Drupal #081 - Drupal 8 - 2016

January 14, 2015

In episode #081 the crew is back together for the first show of 2015 and we talk about Drupal 8s likely release in 2016. We also provide a listener with some feedback on the project.





  • Drupal 8 -  Full release 2016
  • Getting involved and getting started
  • Does this change anything in your mind?How to move forward with Drupal 8
  • Tips on building a volunteer hour tracking website

Module of the Week: 


Paragraphs is the new way of content creation!  It allows you — Site Builders — to make things cleaner so that you can give more editing power to your end-users.

Instead of putting all their content in one WYSIWYG body field including images and videos, end-users can now choose on-the-fly between pre-defined Paragraph Types independent from one another. Paragraph Types can be anything you want from a simple text block or image to a complex and configurable slideshow.

Paragraphs module comes with a new "paragraphs" field type that works like Entity Reference's. Simply add a new paragraphs field on any Content Type you want and choose which Paragraph Types should be available to end-users. They can then add as many Paragraph items as you allowed them to and reorder them at will.

Paragraphs module does not come with any default Paragraph Types but since they are basic Drupal Entities you can have complete control over what fields they should be composed of and what they should look like through the typical Drupal Manage Fields and Manage Display screens.

You can also add custom option fields and do conditional coding in your CSS, JS and preprocess functions so that end-users can have more control over the look and feel of each item. This is way much cleaner and stable than adding inline CSS or classes inside the body field's source.



Hey there,

just another quick thought on Paragraphs, as I started to use it heavily on my last project and I'm really happy how things turned out.

I did create about 7 different paragraph types, such as:
- Big Text, Big Image (with a select field to switch layouts)
- Multicolumn Text with CSS Columns (with a select field to choose column number)
- Grid Text (Floated columns, with a select field to choose columns per row)
- Image Gallery with Title and Intro
- Big Text

Each of these Paragraph bundles is styled with it's own template (and a little template logic where layout selects come into play. This seems like a lot of work initially, but imho it pays off real quick, because:

- My Editors have a lot of freedom to layout pages (each paragraph can be rearranged with drag & drop), while I still have full controll to make each paragraph bundle look really nice
- When I create new content types I simply add a new paragaph field and choose which paragraph types should be allowed for it. All styling is done already, as it uses the paragraphs templates. When I need new elements I create a new paragraph bundle, which again, is a reusable component that I might benefit from in another content type
- Any fieldable entity can benefit form my existing bundle, e.g. I can attach my gallery paragraph to the the user profiles oder to taxonomies.

So Paragraphs allows us to achieve great freedom for "content-design" with easily resuable components. Feels awesome to me :)


Add new comment