We have moved beyond the world of creating pages and into a world where we focus on creating design systems composed of a combination of design aesthetics, ui components, and code standards. In order to communicate these design systems across teams of designers and developers, these design systems are often captured in a living style guide. In this session, we explored how to build and sustain a living style guide. Presented at GiantConf 2016 in Charlotte, NC.
VIP Call Girls Bhiwandi Ananya 8250192130 Independent Escort Service Bhiwandi
Building & Maintaining A Living Style Guide for a Post Apocalyptic Web
1. a Living Style Guide
Building & Maintaining
for a Post-Apocalyptic Web
@mjovel
2. The opinions expressed here are those of the
Presenter and do not necessarily reflect the
positions of the Food & Drug Administration.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22. Department Department Department DepartmentDepartment DepartmentDepartment
Development UX/Design
Sub-DepartmentSub-Department
Delivering the Org Chart
23. Web Staff IT Partner OrganizationsContractors
Department
SME
Delivering the Org Chart
32. Atoms are the basic building blocks of matter.
Applied to web interfaces, atoms are our HTML
tags, such as a form label, an input or a button.
33. Molecules are groups of atoms bonded together and
are the smallest fundamental units of a compound.
These molecules take on their own properties and
serve as the backbone of our design systems.
For example, a form label, input or button aren’t too
useful by themselves, but combine them together as
a form and now they can actually do something
together.
34. Organisms are groups of molecules joined together to
form a relatively complex, distinct section of an
interface.
For example, a masthead organism might consist of
diverse components like a logo, primary navigation,
search form, and list of social media channels.
35. Templates consist mostly of groups of organisms
stitched together to form pages. It’s here where we
start to see the design coming together and start
seeing things like layout in action.
75. Centralized Model Benefits
• Dedicated team avoids single product bias
• Spread design system to many product lines
• Coordinate prioritization of patterns across many products and
manage backlog
76. Centralized Model Problems
• Lack of context of day to day product building
• Lack ability to foster active participation
• Lack of visibility with product teams
78. Federated Model Benefits
• Teams composed of various products reduces single product bias
• Creates evangelists within product teams
• Design system will more accurately reflect product needs.