This is a new and excellent resource from UK-based front-end developer Jaime Caballero designed as a space for information about progressive enhancement. Check out the articles page for a couple of entries from yours truly!
Slides from Tammy Everts‘ 2013 presentation on the neurological effects of poor performance on our websites’ visitors reveal some startling facts. Right out of the gates, Tammy cites a 2010 EEG study of users navigating a site on a connection throttled from 5MB to 2MB. The study found that participants had to concentrate up to 50% harder and reported a negative brand association afterward.
Champion good ideas.
It’s one of LivingSocial’s company values and it’s what I’m here to do today. The idea? Creating the kind of environment where your team is comfortable asking questions & thinking out loud.
My brilliant co-worker Sara on the importance of asking questions and thinking aloud. Few things are more devastating to a company’s culture—and detrimental to the organization’s success—than making team members feel they can’t speak up or ask questions.
America doesn’t have a gun problem. It has several of them.
An intense seven-minute explainer from Vox highlighting the disproportionate rate of gun violence in the United States.
As Jason Kottke wrote when sharing this video:
Easy access to guns turns bad moods, bad politics, bad religion, bad brain chemistry, and bad ideas into murder.
A cool new front-end performance analysis tool from Gaël Métais that offers code improvements.
This is done by loading the webpage via PhantomJS and collecting various metrics and statistics with the help of Phantomas. These metrics are categorized and transformed into scores. It also gives in-depth details so developpers can correct the detected issues.
Yellow Lab Tools dovetails nicely with more popular performance tools like WebPageTest.
I tend not to rely on browser-specific hacks these days, but this is a useful resource should you be in the market for such things.
A community-driven effort to make web accessibility easier.
This is a great resource, chock full of helpful links to tutorials and examples. Be sure to check out the patterns page.
I find myself with IoT talking about progressive enhancement all the time, even though it’s a Web thing, but it makes even more sense. Really, it should be the thing it was designed to be first and then the smarts layered on top.
Stephanie Rieger on a recent episode of The Web Ahead podcast, speaking with Jen Simmons about designing network-connected physical devices—ahem the Internet of Things—with the philosophy of progressive enhancement baked in. Sure, you could build a Web-connected light switch, but if it isn’t first a well-designed light switch, you’ve missed the mark.
Jon Daniel on software maintenance:
I’ve realized that successful applications in an “Enterprise” environment spend far more time in maintenance mode then they do being actively developed. Consumers of your application don’t care that you used some cutting edge framework or state-of-the-art architectural patterns. They just care that it works and continues to work well.
Jon goes deep on operational concerns and posits:
Software is not done until it is decommissioned.
I couldn’t agree more.
Are you building your own website? Indie reader? Personal publishing web app? Some other digital magic-cloud proxy? If so, come by and join a gathering of people with like-minded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, or help work on a project.
The State of Web Type is a project by Bram Stein to collate and display up-to-date browser support data for web fonts & typographic features on the web.
GitHub added the ability for project maintainers to add issue and pull request templates to projects.
To add an Issue template to a repository create a file called ISSUE_TEMPLATE in the root directory. A file extension is optional, but Markdown files (.md) are supported. Markdown support makes it easy to add things like headings, links, @-mentions, and task lists to your templates.
Thinking this will prove quite useful on some of my projects.
Imagination is our window into the future. At NASA/JPL we strive to be bold in advancing the edge of possibility so that someday, with the help of new generations of innovators and explorers, these visions of the future can become a reality. As you look through these images of imaginative travel destinations, remember that you can be an architect of the future.
Chrome’s about to change how it handles
<link rel="stylesheet">. This is big news and Jake‘s got the rundown:
The plan is for each
<link rel="stylesheet">to block rendering of subsequent content while the stylesheet loads, but allow the rendering of content before it. The stylesheets load in parallel, but they apply in series. This makes
<link rel="stylesheet">behave similar to
It’ll take some getting used to sprinkling
<link rel="stylesheet">throughout a page’s
<body>, but the performance benefits (coupled with HTTP/2) will be worth it.
Transfer-Encoding: chunkedheader, the server will send chunks of the rendered page back to the browser so in the case of Rails, it starts with the layout and sends out the
<head>part including assets like js and css.
Chunked transfer encoding is a great way to improve page performance for the parts of your application that require time-consuming database queries. The Rails-level changes are straightforward, but unfortunately not all Ruby web servers support the feature (looking at you, Puma).
Looking for more great links organized by year? Browse the archives.