DrupalCon Nashville 2018
Anton Staroverov
DrupalCamp Stanford 2018
Anton Staroverov
DX-Meetup Basel 2018
Anton Staroverov
#dxmeetup
Hi!
Design System Architect
at
WONDROUS
YOUNG AGENCY
Set of design rules which defines the basics, such as typography, grid, brand, icons, etc.
The most abstract part of UI.
An organized set of related, reusable components, containing code examples, design guidelines, and use cases.
Storage for your components .
The complete set of design standards, documentation, and principles along with the toolkit to achieve those standards.
Connects Style Guide + Pattern Library.
but ugly
but contentless
but custom
generic!
<-- we are here
[ I hope ]
Before beginning work on your design system, take a moment to think about the team you’ll need to bring it to life. Who needs to be involved?
Spoiler alert!
You’re going to need more than just designers.
from Salesforce
A Design System isn’t a Project.
It’s a
Product
, Serving Products.
It's Shifting Focus from Design and Development to Managing and Marketing a System.
Components!
Atoms!
Paragraphs!
Blocks!
Choose names and classifications that make the most sense for the most people. It can be counter-productive if a team spends more time struggling with the analogy than designing and building the tool itself.
from Paravel
Material by Google
Carbon by IBM
Lightning by Salesforce
Polaris by Shopify
Functional Generic Components
with Common Interfaces
Horizontal vs. Vertical
< >
Atomic Carousel
Atomic Gallery
Yarn package containing:
.scss
.twig + data-attrs
.js
.config (Fractal)
Common Interface!
Use as yarn/npm or git
Customize on any level
From No Styling
To Design Systems
And Back
Team Play
Product Mindset
Shared Language
Functional vs. Visual
Horizontal vs. Vertical
Content vs. Design
Building Blocks to Rule 'Em All
Locate this session at the DrupalCon Nashville website:
https://events.drupal.org/nashville2018/sessions/living-design-systems
Take the Survey!
https://www.surveymonkey.com/r/nashiville