- 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.
Straightforward and valuable agenda:
- Differences between Design System vs. Pattern Library vs. Style Guide.
- How to make it [work] serve for your Team.
- How to integrate it all with Drupal.
- How to share the Design language across Team and beyond - to the Client.
Properly organized, Design System should serve for you (not waste your resources!) and make your Frontend, Backend, Designers and Client all happier!
In discussions about accessibility and diversity, our thoughts tend to jump to ARIA links, screen readers, and people of different ethnicities. While these are key aspects to both topics, this talk will push your thinking to considerations beyond accessibility and diversity basics. At its core, embracing accessibility provides us with a launching ramp to usability, and it helps us to serve and support a variety of users.
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.
There are a crazy amount of different approaches for layout management in Drupal today:
- Layout Discovery/Builder
- Block Layout
- Display Suite
- UI Patterns
- Paragraphs (+ Frontend UI)
In this session we will go through all of them and try to make a big picture — what is designed for, and how to use them properly — together, or independently from each other.
Watch the session video here.
Compared to LAMP platforms like Drupal and Wordpress, JAMstack has four huge things going for it:
1. High traffic sites that cost thousands of dollars a month could transition to a single server + CDN on low tier hosting (under 100 dollars a month)
Recently the field of static prototyping, living style guides, and front-end focused development tools has blossomed, and the adoption of these processes has entered into best practices. But we’ve always felt something was missing from this formula and the de-facto tools: Content Strategy.
There's been a lot of talk around the community about decoupling Drupal and using it as headless CMS, or progressively decoupling it and embedding modern JS frameworks inside a Drupal page. But when do you consider just not introducing Drupal and working with a pure framework implementation? And what if you still need to host it alongside Drupal?
How and why to decouple your Pattern lab from your theme. In this case study I will be talking about the decisions taken in the architecture of this solution for the City of San Francisco.