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.
Patterns, Patterns: Design Systems Implementation the Red Hat Way
Design systems are a powerful tool in any company’s arsenal. They provide consistency, support brand recognition, and streamline the design process itself. There are many benefits, but implementing systems across a large product portfolio can be cumbersome for the most nimble of teams.
Watch the session video here.
As site owners, it’s impossible for us to serve our users better without knowing a little bit about them -- what’s working for them, and what isn’t. There are a number of high-impact but unobtrusive ways to learn more about how users interact with your site and your brand. In fact, you might be surprised at the information you can learn about your users with nothing more than Google Analytics.
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.
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:
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.
Watch the session video here.