design

Straightforward and valuable agenda:

1. Differences between Design System vs. Pattern Library vs. Style Guide.
2. How to make it [work] serve for your Team.
3. How to integrate it all with Drupal.
4. 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!

Watch the session video here.

Session Slides are here.

Designing a website can be a very complicated process with a lot of stages depending on the size of the site you are building.

We all know that every good, juicy story must have a compelling beginning that draws the reader in, action throughout and an ending that wraps up the story elements into a satisfying ending. 

Like a good story, a good website needs to draw your desired audience in, keep the user engaged through their journey on your site until they take the desired actions.

In this session, we explore how to write that story.  Utilize this no-fail approach to outlining the needs and requirements of your organization and audience to ensure that everyone gets the results they’re looking for.

The decentralized web is rapidly gaining steam in privacy and security circles as the promise of a "Web 3.0" begins to take hold. Nonetheless, among all of the challenges facing the nascent decentralized web, perhaps none is as pressing as user experience. Though many tout network effects and convenient features as the leading factors that led to the Big Tech walled gardens characterizing the web today, the attractive and seamless user experiences that the closed web offers are far too frequently ignored.