Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Design Systems and Component Based Frontend
Search
Bilal Çınarlı
June 27, 2019
Programming
0
120
Design Systems and Component Based Frontend
Bilal Çınarlı
June 27, 2019
Tweet
Share
More Decks by Bilal Çınarlı
See All by Bilal Çınarlı
Accessible By Default!
bcinarli
0
53
Aninda Yüklenen Uygulamalar
bcinarli
0
100
Iletisimin Mühendisligi
bcinarli
0
53
Independently together: better developer experience & App performance
bcinarli
1
460
Developer Experience: How happy are your engineers?
bcinarli
0
260
Micro Applications: Divide & Conquer
bcinarli
2
1.1k
Lightning Fast Web Applications
bcinarli
1
540
WebAssembly - is it the future for the Web?
bcinarli
0
130
Why Performance Matters
bcinarli
0
170
Other Decks in Programming
See All in Programming
Is Xcode slowly dying out in 2025?
uetyo
1
250
なんとなくわかった気になるブロックテーマ入門/contents.nagoya 2025 6.28
chiilog
1
260
Systèmes distribués, pour le meilleur et pour le pire - BreizhCamp 2025 - Conférence
slecache
0
120
git worktree × Claude Code × MCP ~生成AI時代の並列開発フロー~
hisuzuya
1
540
ペアプロ × 生成AI 現場での実践と課題について / generative-ai-in-pair-programming
codmoninc
1
13k
なぜ「共通化」を考え、失敗を繰り返すのか
rinchoku
1
640
エンジニア向け採用ピッチ資料
inusan
0
180
PHP 8.4の新機能「プロパティフック」から学ぶオブジェクト指向設計とリスコフの置換原則
kentaroutakeda
2
740
0626 Findy Product Manager LT Night_高田スライド_speaker deck用
mana_takada
0
150
A full stack side project webapp all in Kotlin (KotlinConf 2025)
dankim
0
100
PHPでWebSocketサーバーを実装しよう2025
kubotak
0
270
Select API from Kotlin Coroutine
jmatsu
1
220
Featured
See All Featured
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Build your cross-platform service in a week with App Engine
jlugia
231
18k
Docker and Python
trallard
44
3.5k
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
48
2.9k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
8
680
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
26k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
35
2.4k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
How To Stay Up To Date on Web Technology
chriscoyier
790
250k
Why Our Code Smells
bkeepers
PRO
337
57k
VelocityConf: Rendering Performance Case Studies
addyosmani
332
24k
Transcript
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