We will look at the current state of responsive and lazy-loaded images on the web. We will see at the multiple ways of achieving these techniques in Drupal using a combination of contributed modules and Drupal 8 core modules. We will also look at the results of several benchmark tools before and after we apply the techniques covered. For responsive images, we will see how far we can get using just Drupal 8 core modules and what are the main use cases for responsive images. For lazy loading images, we will look at multiple contributed modules that let you achieve this technique and how to implement this on the theming level. The best formats and ways to optimize images will also be covered in this presentation, we will go over formats and different types of compression we can use to deliver our images faster to users.

Entities are an integral part of the Drupal ecosystem and almost every entity in Drupal is linked with forms. Thus Drupal provides a beautiful Form API that helps in building, validating and submission of forms. All three stages are very important and have their own significance. But our focus throughout the session will be the form validation aspect.

To perform custom server-side validations on forms we often write #validate functions in Drupal which always do the job. But there are some negatives to it, Example: Validations don’t run when you try creating/editing the entity via means other than entity form. Perhaps this problem was assessed and tackled in Drupal 8 by the introduction of Entity validation constraints.

In this session we will be learning about the following:

• Problem with form API validation

• Creating custom validation constraint

• Applying validation constraint to the entity field

• Applying validation constraint to the entity

• Running validations for REST API requests

• The Demo

At the end of this session, users will have a clear understanding of how decoupling entity validation from entity forms allows validations to be independent of form submissions.

If the internet was a 
country, it would rank
 6th for electricity usage and 1.700 M tons is the current size of the internet's annual carbon footprint. Since we cannot simply remove the internet from our lifes, we need to make sure that what we put out there has as little impact as possible. I will show you some examples on how we can make our products as green as possible.

Drupal can be your perfect technical SEO platform, but to get the most out of it, you have to make sure it's set­ up like it should be for the search engines, and there are a number of easy to miss issues that can have a big negative impact on your site’s organic visibility. By default, Drupal isn’t bad at all in supporting SEO, but in this session, we’ll go into detail on how to find and fix problems, and how to prevent them in the future.

We will go into the details of how to detect SEO issues common and rare (on real Drupal sites!) and explain their impact on SEO: from indexed internal search pages, invalid sitemaps, indexed test environments to interesting challenges with pagers, multilingual metatags, and more.

Of course, we’ll show you how to solve all these issues when you find them, but more importantly, we’ll show you how to prevent them in the first place.

When you leave this session, you will understand there's more to SEO in Drupal than enabling a couple of modules. We’ll give you methods and guidelines to detect, fix, and prevent problems to develop high quality Drupal sites with SEO in mind.

Wouter De Bruycker, SEO Specialist, is experienced with the ins and outs of Drupal site audits, and getting the best SEO visibility out of Drupal.

Brent Gees, Drupal Architect, implements the technical fixes discovered in Wouter’s SEO audits and has his own bag of tricks for solving them, from configurations to patches, the right contrib. module, or custom code. Every solution has its place in supporting the work that your content teams put into your content.

This will be an extended and improved version of the session given at Drupalcon Amsterdam (https://drupal.kuoni-congress.info/2019/program/abstract/186)

In this session, we will try to explain how Netflix’s personalization approaches to display tailored content to each user can be implemented in Drupal using existing modules and technologies. 

Drupal is the CMS of choice when it comes to creating content rich sites. However, it is no longer enough to display the same content to all users. In a world where diversity is increasingly obvious and celebrated, websites have to step up their game and adapt to a wide range of users and their preferences. This is where Personalisation comes in. While Netflix personalization is complex and composed of thousands of algorithms, it can be broken down into distinct use cases which can then be solved independently.

Presentation Flow:

1. Why Personalize

2. Understanding Netflix personalization use-cases

3. Getting started with Personalization your Drupal solution
   -- Comparison of existing modules/technologies

4. Solving Netflix like personalized use-cases in Drupal
   -- Applying modules to different use-cases
   -- Comparing different Drupal personalisation modules for solving the same use-case.

Terraform is the defacto champion of Infrastructure as Code and provisioning. GitLab provides the perfect platform for managing code, CI and containers from development to production. AWS is the leader in Infrastructure as a Service.

In this talk, I will introduce the audience to a complete pipeline to build and transfer applications from GitLab to AWS using Terraform and GitLab CI.

Along the way we will:

1. Provision and manage our infrastructure with Terraform
2. Configure our infrastructure with Ansible (both mutable and immutable)
3. Secure with Vault
4. Manage it all in GitLab CI pipelines making it all versionable, auditable and visible
5. Have fun (hopefully).