architecture

• Reusable Patterns (Frontend Components) vs Web Components.
• Separation of concerns (aka MVC): styling, functionality, data.
• Yarn Workspaces to maintain separate component and manage its dependencies.
• data- attrs to control components in a declarative way and w/o js.
• Twig to build all together.
• Using with Drupal or other CMS.
• Using with Fractal or other pattern library.
• Demos: Reusable Carousel, Reusable Gallery, Reusable Modal, compound components.

This session is the fourth one in the series, following the How to Content Model in Drupal 8 at DrupalCon Vienna 2017, Drupal 8 Hidden Power at DrupalCon Dublin 2016 and Drupal Architectures for Flexible Content at DrupalCon Barcelona 2015.

It used to be easy to deploy applications, you just deploy a VM on DigitalOcean, SSH into it, set up your LAMP stack and go from there.

What is all the excitement about AWS, Provisioning, Docker, Kubernetes, Serverless? You are still using DigitalOcean and are happy with it? If you asked yourself that question, I will give you the answer.

This session will walk you through the evolution of application deployment strategies and practices, starting from manual server deployment and ending in cloud infrastructure orchestration best practices.

You will learn:

Drupal deployments are hard. You have to make sure your code is deployed, composer dependencies are pulled, schema updates are performed and caches cleared, all with keeping the website up and responsive for the users, add the fact that you host on multiple servers and you have active users online updating some content 24/7 and it gets even more interesting. What if anything goes wrong and you want to rollback, do you have to deploy again and have your users wait?

The answer is No. Blue/Green deployments are the solution to this problem, but how do we do that with Drupal?

Volunteering is cool, nobody questions that, but we are all pragmatic humans and thus need motivation. In this session I will share with you reflections derived from my experience of contribution to open source. Mostly it has been Drupal (6 years) and just recently initiated Gentoo Linux (6 months). During these 6 years I grew as a contributor to the status of a co-maintainer of Webform 8.x module.

Is your Drupal site is more than a just website?  Is it instead an application with hundreds of fields and gigabytes of data? You've probably already realized the difficulty of reporting and analytics from your production site.  This session will explore ways you can flatten your data and move it to a reporting instance on AWS for reporting, analytics, and even microservices. This session will also highlight opportunities for automation along the way.

Drupal 8's Configuration Management System is a modern marvel. We now have a standard way to export, store, and import configuration files.

When working on a single site, built on a fresh Drupal 8 install, the process is pretty straightforward and there are many tools to help along the way.

But what if you're building lots of similar sites? Like a multi-site? Or maybe a Drupal Distribution? Or Install Profile? Or Sub-Profile? In Drupal 7 we had Features. Do we still need that?

Nobody loves writing or responding to a request for proposals (RFPs) but it is often a necessary process. In this session, we will discuss the steps it takes to write a good website RFP, but also how to attract the right vendors to bid and what to do to make this process an educational and meaningful experience.

In this tactical session you will learn:

Watch the session video here.

The average lifespan of a website is 3 years.  Drupal 7 will be end-of-life in 3 years. 

If your site is in Drupal 7 you are likely asking yourself what to do. Is it time to start from scratch and rebuild, or can you maximize what you have?

There are lots of options and in this session, we will cover how to: 

Have you ever wondered about the implications of your architectural decisions? Should an entity reference go on this entity type or that one? Why? Is it ok to nest many different entity types together? How many is too many? How many levels down? Paragraphs? Why? Fields or entity displays? When and why?