The stomach flu descended on our family this week and, while I didn’t get sick, I’ve been taking care of others who did. As a result today’s post is a group of links I’ve been reading and thinking about related to webdev and QA rather than something original.
http://css-tricks.com/modular-future-web-components/
[Web Components] allow us to bundle markup and styles into custom HTML elements. What’s truly amazing about these new elements is that they fully encapsulate all of their HTML and CSS. That means the styles that you write always render as you intended, and your HTML is safe from the prying eyes of external JavaScript.
Two things here. I’ve heard about the Shadow DOM recently but hadn’t really explored it or understood what it was about till I read this post. Secondly, this concept looks pretty cool and I can definitely see how it will be useful in the future as adoption increases.
If you work on WordPress sites with a team or even maintain multiple WordPress sites on your own and feel like something is missing in your infrastructure you need to read this article. It presents a very interesting view of how to manage and maintain WordPress sites with version control and dependency management.
http://www.mobilecommercedaily.com/new-direction-needed-for-mobile-web-site-performance
performance is one of the most important differentiators when it comes to mobile adoption, use and customer satisfaction
The knowledge that the mobile interface is different from the desktop one doesn’t always mean that we give mobile the effort it needs to shine. This is of course going to depend on your business focus, but this article lists some concrete observations and tips to make mobile better.
Self-Executing Anonymous Functions or How to Write Clean JavaScript
A bit of hyperbole but a good look at self-executing anonymous functions – how to write them and how they can be used. Also, I learned about the existence of jQuery.proxy which makes it easy to wrap functions as arguments to preserve the current context.
http://24ways.org/2013/why-bother-with-accessibility/
Accessibility is frequently something that gets tacked on to a project at the end to meet a bullet in the requirements list. Here are 4 excuses for this and rebuttals for why maybe it shouldn’t be this way.