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
The purification of web development
Search
Nicolas Gallagher
May 30, 2013
Programming
5
410
The purification of web development
Nicolas Gallagher
May 30, 2013
Tweet
Share
More Decks by Nicolas Gallagher
See All by Nicolas Gallagher
React Native for web and beyond
necolas
5
960
Thinking beyond "Scalable CSS"
necolas
14
6.8k
Making Twitter UI Infrastructure
necolas
14
4k
Adaptation and Components
necolas
6
1.2k
CSS Application Architecture
necolas
15
550
HTML5 Boilerplate: past, present, and future
necolas
4
250
Other Decks in Programming
See All in Programming
Modernisation Progressive d’Applications PHP
hhamon
0
110
How to Break into Reading Open Source
kaspth
2
220
A New Era of Testing
mannodermaus
2
530
rbs-inlineを導入してYARDからRBSに移行する
euglena1215
1
300
Method Swizzlingを行うライブラリにおけるマルチモジュール設計
yoshikma
0
120
Why Prism?
kddnewton
4
1.7k
Modern Angular with the NGRX Signal Store New Rules for Your Architecture @BASTA! 2024 in Mainz
manfredsteyer
PRO
0
160
意外とフォントが大事だった話 / Font Issues on Internationalization
fumi23
0
110
Go1.23で入った errorsパッケージの小さなアプデ
kuro_kurorrr
2
400
rails_girls_is_my_gate_to_join_the_ruby_commuinty
maimux2x
0
200
いまから追い上げる、Jetpack Compose トレーニング
nyafunta9858
0
620
LangChainでWebサイトの内容取得やGitHubソースコード取得
shukob
0
160
Featured
See All Featured
Art, The Web, and Tiny UX
lynnandtonic
294
20k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
326
21k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
41
6.5k
Building an army of robots
kneath
302
42k
ParisWeb 2013: Learning to Love: Crash Course in Emotional UX Design
dotmariusz
109
6.9k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
5
490
Rails Girls Zürich Keynote
gr2m
93
13k
Fashionably flexible responsive web design (full day workshop)
malarkey
401
65k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
89
16k
Faster Mobile Websites
deanohume
304
30k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
230
17k
GitHub's CSS Performance
jonrohan
1030
450k
Transcript
The purification of web development
Nicolas Gallagher @necolas
Before code…
Assumptions and the history of ideas
Heraclitus (535 BC – 475 BC)
None
Democritus (460 BC – 370 BC)
None
None
“You cannot step twice into the same river; for fresh
waters are flowing in upon you.” – Heraclitus
CSS and the purification of HTML
<table> <tr> <td align="left" onClick="dothing()"> <center> <font face="verdana">…</font> </center> </td>
</tr> </table>
“To increase the granularity of control over elements, a new
attribute has been added to HTML: 'CLASS'.” - CSS1 spec
None
Don’t use “unsemantic” class names?
“Your HTML, like diamonds, should be forever.” - camendesign.com
“…authors are encouraged to use [class attribute] values that describe
the nature of the content, rather than values that describe the desired presentation of the content.” - HTML5 spec
“A structure based on CLASS is only useful within a
restricted domain, where the meaning of a class has been mutually agreed upon.” - CSS1 spec
Class names are for us, not machines
We can pick our own meaning
Don't write ugly class names?
<p class="hyphens-as-word-separators"> … </p>
/* Component */ .button {…} /* Component */ .button-group {…}
/* Component modifier */ .button.primary {…} /* Component child */ .button-group .item {…}
/* Component */ .Button {…} /* Component modifier */ .Button--primary
{…} /* Component */ .ButtonGroup {…} /* Component descendant */ .ButtonGroup-item {…}
<!-- HTML --> <ul class="ButtonGroup"> <li class="ButtonGroup-item"> <button class="Button"> Save
</button> </li> <li class="ButtonGroup-item"> <button class="Button Button--cancel"> Cancel </button> </li> </ul>
None
github.com/necolas/suit-button-group
github.com/necolas/suit
Structured class names are useful
Don’t use extra elements?
<article class="Box"> <div class="Box-close"> <button class="u-textLike js-close"> <span class="Icon Icon--close"></span>
<span class="u-isHiddenVisually"> Close </span> </button> </div> ... </article>
<article class="Box"> <div class="Box-close"> {{> partials/close-button }} </div> {{$content}}{{/content}} </article>
{{<box_with_close}} {{$content}} <h1>Title</h1> <p>Some words</p> {{/content}} {{/box_with_close}}
Look at what they make you give
Web Components
“Web Components…let web application authors define widgets with a level
of visual richness not possible with CSS alone” - W3C Introduction to Web Components
“…specify the extra presentation using markup…” - W3C Introduction to
Web Components
None
Encapsulation, interoperability, reuse
Shadow DOM Encapsulation and DOM boundaries <element> Custom elements; extend
native elements <template> Clonable, inert DOM fragments
<element extends="button" name="x-btnClose"> <template> <style> @host { /* css to
unstyle button */ } .visHidden { /* css to hide text */ } </style> <x-icon type="close" size="24"></x-icon> <div class="visHidden"> <content></content> </div> </template> <script>// javascript</script> </element>
<button is="x-btnClose">Close</button>
None
It’s ok to rely on extra elements
Step back into the river
The end