Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Design Systems and Component Based Frontend
Search
Bilal Çınarlı
June 27, 2019
Programming
180
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Design Systems and Component Based Frontend
Bilal Çınarlı
June 27, 2019
Transcript
57 slides
Design Systems & Component Based Frontend
Bilal Çınarlı Frontend Architect Software Engineer @Adidas @bcinarli github.com/bcinarli bcinarli.com
None
Harmony from Intuit, GEL – Global Experience Language from BBC,
Material from Google, Lightning from Salesforce, AirBNB’s Visual Language, Joystick from EA, Fluent from Microsoft, Plasma from WeWork, Polaris from Shopify, Lonely Planet, Swarm from Meetup, Canvas from Hubspot …and aDL from Adidas
What is a design system?
A collection of reusable components, guided by clear standards, that
can be assembled together to build any number of applications.
None
A design system is a combination of style, components, and
voice.
It is scalable at any level
Provides consistency between different pages and applications
With the set of rules and guides, increases the efficiency
Enhances the teamwork and eases the on-boarding of new members
http://bit.do/yarnds
http://bit.do/adl_
Components
Components support levels of abstraction in an application. It is
layered and feature-based.
Individual components provide decoupling which leads to better unit testings
and stability.
Design system and Components combine mostly in UI layer where
your presentation occurs
Besides, components can also communicate with the data layer while
rendering our content.
…and with the standardisation, it improves quality.
None
How Popular Libraries Think?
Build encapsulated components that manage their own state, then compose
them to make complex UIs.
Components define areas of responsibility in your UI that let
you reuse these sets of UI functionality.
It’s an abstraction that allows us to build large-scale applications
composed of small, self-contained, and often reusable components.
But the mainly, they should have a responsibility over a
single part.
None
How to Organise?
Define your folder structure based on their functionalities
Think of everything is sort-of a pluggable component. In most
cases, when you remove it, you should expect no traces left.
// DON’T . !"" controllers | !"" cart.js | #""
checkout.js !"" models | !"" cart.js | #"" checkout.js #"" views !"" cart.pug #"" checkout.pug // DO . !"" cart | !"" index.js | #"" template.pug #"" checkout !"" index.js #"" template.pug
…and tests are a part of your components.
// add test specs . !"" cart | !"" index.js
| !"" test.spec.js | #"" template.pug #"" checkout !"" index.js !"" test.spec.js #"" template.pug
Separate config and scripts away from your components.
. !"" config | !"" index.js | #"" server.js !""
scripts | !"" build.sh | #"" post-install.sh !"" test | !"" index.js | #"" setup.spec.js !"" cart | !"" index.js | !"" test.spec.js | #"" template.pug #"" checkout !"" index.js !"" test.spec.js #"" template.pug
Keep HTML and CSS separate in your source code and
never inline manually
// DON’T <p style="margin: 10px 0; padding: 0;">Hello World! </p>
// DO .content-text { margin: 10px 0; padding: 0; } <p class="content- text">Hello World!</p>
Always think about specificity in CSS, try to avoid creating
specific selectors
// DON’T #main .article .title span { font-size: 32px; font-weight:
bold; } // DO .main-article-title { font-size: 32px; font-weight: bold; }
Do not write the code you are going to overwrite
// DON’T .content { display: flex; max-width: 1280px; margin: 0
auto; } .article { width: 900px; } .supplementary { width: 380px; } @media screen and (min-width: 48.0625em) and (max-width: 64em) { .article { width: 644px; } } @media screen and (max-width: 48em) { .content { flex-direction: column; } .article, .supplementary { width: 100%; } } // DO .content { max-width: 1280px; margin: 0 auto; } @media screen and (min-width: 48.0625em) { .content { display: flex; } .article { flex: 1; } .supplementary { width: 380px; } }
A way to unify different frameworks?
Web components are a set of web platform APIs that
allow you to create new custom, reusable, encapsulated HTML tags to use in web pages and web apps.
Custom components and widgets build on the Web Component standards,
will work across modern browsers, and can be used with any JavaScript library or framework that works with HTML.
<script type="module" src=“components/nav/app- drawer“></script> <app-drawer raised class=“indigo">raised</app-drawer>
<script> class AppDrawer extends HTMLElement {...} window.customElements.define('app-drawer', AppDrawer); </script> <app-drawer></app-drawer>
Good part, all JS frameworks outputs to HTML. Theoretically, we
can use any popular JS library to create Web Components
What is more?
Having self-contained, reusable components helps to turn you app to
micro frontends
… that can have independent deployment, build, coding
… leads to autonomous teams
… and you can have a shell that orchestrates which
micro frontend to load
… with the “Best Friend of Frontend"
Your components should not know what the dependencies are in
behind the curtains you are using.
It should only aware of which functions are available for
a particular action.
Every dependency comes with a technical debt for the future.
Thank you @bcinarli
More Decks by Bilal Çınarlı
See All by Bilal Çınarlı
Efficieny and Scaling in Frontend
bcinarli
0
75
Navigating with Unknowns
bcinarli
1
58
Story of a Boring Work
bcinarli
0
40
Refactoring Frontend
bcinarli
0
72
Accessible By Default!
bcinarli
0
130
Aninda Yüklenen Uygulamalar
bcinarli
0
160
Iletisimin Mühendisligi
bcinarli
0
75
Independently together: better developer experience & App performance
bcinarli
1
590
Developer Experience: How happy are your engineers?
bcinarli
0
310
Other Decks in Programming
See All in Programming
Materialが消えた日 〜真っ白なFlutterキャンバスにRenderObjectで絵を描く〜
umigishiaoi
0
170
クラウドゲーミングのパフォーマンス最適化に挑む / Cloud Gaming Performance Tuning
vivion
0
360
AI時代のシニアエンジニアとは
yosuke_furukawa
PRO
15
12k
止まらない比較を止める — 余帰納法で無限ストリームを比べる
tarao
0
210
AIが生成したコードは読むべきか?抽象化設計とコードの品質保証 / abstraction-design-and-quality
minodriven
17
9.5k
The Cost of the DOM
ypresto
2
210
AI時代のFlutter品質設計 — アプリ品質を守るQuality Layers
omatty198
0
390
LLM 101
dalinaum
0
540
Enforcing Your Architecture with Unit Tests in the AI Era (Swift Connection X)
steliosf
PRO
1
190
AI駆動開発4年目の現在地(『あなたはFDEになるべきか?』イベント資料)
kumaiu
0
700
Skills Are the New npm [AAIF Bengaluru, Nov 2026]
shivamsaraswat
0
120
[DroidKnights 2026] Workflow AX 적용기 — 자동 정책 정리부터 E2E까지
dayeon
0
120
Featured
See All Featured
Side Projects
sachag
456
43k
Are puppies a ranking factor?
jonoalderson
2
4.2k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
508
140k
Pawsitive SEO: Lessons from My Dog (and Many Mistakes) on Thriving as a Consultant in the Age of AI
davidcarrasco
1
320
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
3k
Done Done
chrislema
187
17k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
9
1.7k
Building the Perfect Custom Keyboard
takai
2
970
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
133
20k
Deep Space Network (abreviated)
tonyrice
0
430
How GitHub (no longer) Works
holman
316
150k
Lightning Talk: Beautiful Slides for Beginners
inesmontani
PRO
2
860