How do you sell Web Standards?
Don't sell. Show.
The Angular Mini-Book is a
guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and
deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.
Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.
For book updates, follow @angular_book on Twitter.
The JHipster Mini-Book is a
guide to getting started with hip technologies today: Angular, Bootstrap, and Spring
Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.
This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.
For book updates, follow @jhipster-book on Twitter.
Did you know that IE6/Win does not know the difference b/w dotted and dashed - view this post in Mozilla to see how it's really supposed to look. Maybe their next release will be more standards-compliant. This happens even with standards-compliant mode turned on.
The station I found yesterday DOES broadcast Mark and Brian - awesome! It's actually one of the best internet radio broadcasts I've ever heard (besides the network drops), they play music during the commercials to get around the internet radio issue.
Rick Salsa seems to sum up "what's new" in XHTML 2.0 a lot better than my previous post.
I changed this site to use font-size: 70%
from font-size: 11px
so you could resize the fonts on this site using your browser. This is a workaround for what Zeldman describes today.
<quote>
All modern browsers now offer Text Zoom or Page Zoom but one: IE/Win. Which is, of course, the most-used browser on earth. The IE/Windows team has done great things, but implementing Text Zoom is not one of them.
</quote>
To me, changing your css to use a percentage value rather than a pixel value (i.e. 12px -> 80%) seems like a pretty easy workaround.
Did you know that XHTML 2.0 is already in the works? As you all throw up your hands and say, "Geez we were just getting to know XHTML 1.0 (and 1.1)," I'm here to tell you that there haven't been many changes since XHMTL 1.1.
Here is an example XHTML 2.0 page.
Zeldman turned me on to it. Web Standards for Hard Times is a great read for anyone that is (1) starting to develop a new website or (2) wondering why their site looks different in different browsers. The best thing to know:
Many developers still don't realize that newer browsers look for a
DOCENGINE tag at the top of each page, and will change the way they
behave in response to it. Without the correct tag, browsers can take
your standards-compliant page and render it all wrong.