There are lots of clever one-lin­ers for gen­er­at­ing ran­dom col­ors. Un­for­tu­nately, this code nat­u­rally pro­duces murky greys, browns and greens. ran­dom­Color gen­er­ates at­trac­tive col­ors by de­fault. More specif­i­cally, ran­dom­Color pro­duces bright col­ors with a rea­son­ably high sat­u­ra­tion.

Font Face Observer is a fast and simple web font loader. You can use it to load fonts and customise your browser’s font loading behaviour.

Get the current accessibility support status of HTML5 features across major browsers.

The internet has become an essential way to access and provide information and services. It is therefore more important than ever to make sure that everyone can perceive and understand websites and mobile apps, and interact with them properly.

For two years, Electron has lowered the barrier to developing desktop applications—making it possible for developers to build cross-platform apps using HTML, CSS, and JavaScript.

Google Chrome developers are planing to implement async/await functions.

Mozilla is extending JavaScript with a primitive API that lets programmers use multiple workers and shared memory to implement true parallel algorithms in JavaScript.

Ravi Kiran introduces you to jspm and SystemJS that let you load any module format (ES6, AMD, CommonJS and globals) directly from any registry.

Examples of most common page layouts.                                                  

Embracing fluid typography might be easier than you think. It has wide browser support, is simple to implement and can be achieved without losing control over many important aspects of design. Unlike responsive typography, which changes only at set breakpoints, fluid typography resizes smoothly to match any device width. It is an intuitive option for a web in which we have a practically infinite number of screen sizes to support. Yet, for some reason, it is still used far less than responsive techniques.

When will vanilla CSS be good enough to replace Sass, Less, Stylus, and the rest?

Simplified JavaScript Jargon (short SJSJ) is a community-driven attempt at explaining the loads of buzzwords making the current JavaScript ecosystem in a few simple words. The idea is not to replace individual documentations, but to act as some kind of glossary that can be easily referenced.

Tim Baxter’s recent A List Apart article, Meaningful CSS: Style Like You Mean It, has once again re-ignited the debate that front-end developers who prefer to take an object oriented approach to CSS with BEM (or similar) somehow forego any concern with semantic markup and accessibility.

Have you ever tried scrolling a dialog and seeing the page scroll in the background?  Awful user experience, bordering on embarrassing.  Yikes.

Good comments make for good collaboration. Ethan talks about what makes CSS comments beautiful, and how you can up your commenting game to score more birthday cards.

Motivated by the regrettably uneven browser support landscape for Service Workers, there’s a real incentive to “just make something work offline” on iOS or old-IE. This phrasing obscures the primary experience difference between native apps and web content: native apps always “boot” when you tap on them. The legacy web, however, can take as long as the TCP timeout (2 minutes in many devices) to end in failure. That’s a looooong time to be looking at a white screen.

As with most things, there are exceptional circumstances in which following the rules would be a pretty bad idea, and it’s usually context and discretion that inform our decision to break them.

As we’re all probably well aware by now, specificity is one of the quickest ways to get yourself in a tangle when trying to scale a CSS project: even if you have the most considered source order, and your rulesets cascade and inherit to and from each other perfectly, an overly-specific selector can completely undo all of it.

Multiple severe and trivially exploited vulnerabilities in ImageMagick were disclosed a week ago, and are known to be exploited in the wild.