Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature1 #67

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions walter-alvarez.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>Of Patterns and Power: Web Standards Then & Now</title>
<meta name="description" content="Web Standards">
<meta name="description" content="Web patterns and power">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 descriptions?

<meta charset="utf-8">
</head>
<body>
<nav role="navigation">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why <nav> here?

<header>
<h1>Of Patterns and Power: Web Standards Then & Now</h1>
</header>
<img src="patter-power.jpg">
<article>
<p>IN <a href="http://danielmall.com/articles/content-display-patterns/">CONTENT Display Patterns</a>(which all front-end folk should read), Dan Mall points to a truth not unlike the one Ethan Marcotte shared last month on 24 ways.It is a truth as old as standards-based design:Construct your markup to properly support your content (not your design).</p>
<p>Modular <a href="http://bradfrost.com/blog/post/atomic-web-design/">atomic design </a> doesn’t change this truth, it just reinforces its wisdom. <a href="https://css-tricks.com/snippets/css/a-guide-to-flexbox/"> Flexbox </a> and grid layout don’t change this truth, they just make it easier to do it better. HTML5 doesn’t change this truth, it just reminds us that the separation of structure from style came into existence for a reason. A reason that hasn’t changed. A reason that cannot change, because it is the core truth of the web, and is inextricably bound up with the promise of this medium. </p>
<p> Separating structure from style and behavior was the web standards movement’s prime revelation, and each generation of web designers discovers it anew. This separation is what makes our content as backward-compatible as it is forward-compatible (or “future-friendly,” if you prefer). It’s the key to re-use. The key to accessibility. The key to the new kinds of CMS systems we’re just beginning to dream up. It’s what makes our content as accessible to an ancient device as it will be to an unimagined future one.</p>
<p> Every time a leader in our field discovers, as if for the first time, the genius of this separation between style, presentation, and behavior, she is validating the brilliance of web forbears like Tim Berners-Lee, Håkon Wium Lie, and Bert Bos.</p>
<p> Every time a Dan or an Ethan (or a Sara or a Lea) writes a beautiful and insightful article like the two cited above, they are telling new web designers, and reminding experienced ones, that this separation of powers matters.</p>
<p> Why is it slippery? Because too many developers and designers in our amnesiac community have begun to believe and share bad ideas — ideas, like CSS isn’t needed, HTML isn’t needed, progressive enhancement is old-fashioned and unnecessary, and so on. Ideas that, if followed, will turn the web back what it was becoming in the late 1990s: a wasteland of walled gardens that said no to more people than they welcomed. Let that never be so. We have the power.</p>
<p> As Maimonides were he alive today, would tell us: he who excludes a single user destroys a universe. Web standards now and forever.</p>
</article>
<footer>
<p><em>Originally published at <a href="http://www.zeldman.com/2016/01/05/13913/">www.zeldman.com</a>
</body>
</html>