The big problem with this process relates to User Experience Design. No one is even discussing what we would try and build and how it would work. We advise our clients to understand their problem and their users before spending time solutioneering, this is twelve levels deeper than that. Drupal has a development driven culture, it always has. I'm not surprised people are more interested in debating the framework of the week instead of looking at the problems it could be solving.

The big problem with this process relates to User Experience Design. No one is even discussing what we would try and build and how it would work. We advise our clients to understand their problem and their users before spending time solutioneering, this is twelve levels deeper than that. Drupal has a development driven culture, it always has. I'm not surprised people are more interested in debating the framework of the week instead of looking at the problems it could be solving.

Most large Drupal sites, and some smaller ones, require per environment configuration. Prior to Drupal 8 this was usually achieved using a combination of hard coding config variables and features. Drupal 8 still allows users to put config variables in the settings.php file, but putting config in code feels like a backward step given D8 emphasis on separating concerns.

To utilize Paragraphs to its full potential you need to learn how to create a container paragraph type and nest paragraph items. The concept of a container is fairly simple. It's a paragraph type that has its own paragraph field on it and allows a user to nest paragraph items.

To utilize Paragraphs to its full potential you need to learn how to create a container paragraph type and nest paragraph items. The concept of a container is fairly simple. It's a paragraph type that has its own paragraph field on it and allows a user to nest paragraph items.