Just as every instance of “the cloud” can be replaced with “the moon” or “my butt”, so too can every instance of the word “markets” in business reporting be replaced with the word “dragons”.
James has got you covered with this bookmarklet to do just that.
The dragons reacted strongly to the news.
This is wonderful stuff! I’m a big fan of the
datalist element but I hadn’t realised how it could be combined with
input types like
Jeff Noon and Markov chains—a heavenly match by Dan.
Here are some nice patterns that Paul uses for starting points in his own projects.
Related to my rant on links that aren’t actually links: buttons that aren’t actually buttons.
You’re probably doing each of these already but just in case your’e not, Andy has listed six quick wins you can get from HTML5.
Bruce takes a look at the tricky issue of styling native form controls. Help us, Shadow DOM, you’re our only hope!
A good explanation of HTML5’s sectioning content and outline algorithm.
Bruce sits down for a chat with Hixie. This is a good insight into the past and present process behind HTML.
Here’s a treasure trove of web history: an archive of the www-talk list dating back to 1991. Watch as HTML gets hammered out by a small group of early implementors: Tim Berners-Lee, Dave Raggett, Marc Andreessen, Dan Connolly…
I love that Tantek is as pedantic as I am …although I don’t think “pedantic” is exactly the right word.
Tantek has put together a wiki page to document the arguments for and against adding a new “main” element to HTML.
An excerpt from Mark’s forthcoming book, which promises to be magnificent.
A handy step-by-step guide to scraping HTML to get data out. Useful for services (—cough—Twitter—cough—) that keep changing the rules of their API use.
A lovely new service from Mike Stenhouse: install the bookmarklet and then when you come across a website with a nice combination of fonts, you can save a snapshot of the page (and its fonts) for later perusal. You can then browse those fonts on Typekit, Fontdeck, MyFonts or Google Fonts.
The Guardian’s front-end patterns library. The modules section contains their equivalent of a pattern primer. Very nice!
Less wireframing, more prototyping.
Bruce’s thoughts on the proposed inclusion of a “content” or “maincontent” element in HTML5.
Personally, I don’t think there’s much point in adding a new element when there’s an existing attribute (role=”main”) that does exactly the same thing.
Also, I don’t see much point in adding an element that can only be used once and only once in a document. However, if a “content” or “maincontent” element could be used inside any sectioning content (section, article, nav, aside), then I could see it being far more useful.
Any sufficiently advanced Markov chain is indistinguishable from James Bridle.
A fun bit of Markov chaining of your tweets. Some of mine:
Had a burrito in Barcelona. Thank you get the peacocks plumage.
Stand by to the most helpful. The Fuck Was That type shop and David Byrne walked into a Wikipedia entry?
Last Waltz again. This Is A demonstration of The office doors are they talk right now. Cool your plans.
Picking salad leaves from the people who own them. They’re just resting” at the communal testing lab is!
Heading out the standard option. Alas, there’s no signs of spending Bloomsday as constructive feedback?
A really great markup and CSS pattern for “content first, navigation second” from Aaron.
Markov-generated Quora questions …far more entertaining than actual Quora questions.
Some sensible advice from Oliver Reichenstein. Cluttering your social media icons isn’t helping and may actively be hindering your audience.
An interesting approach to squishing down large data tables for small-screen viewing …though I wonder if there isn’t a “Mobile First” approach that could scale up, say, lists to become tables on large screens.
Have you thought “There must be a good reason for the blink element.” Well, read on.
The hitherto unnoticed connection between the names of Android phones and the names of condoms.
I really like what Tom has done here, printing out his bookmarks.
They capture a changing style of writing. They capture changing interests – you can almost catalogue projects by what I was linking to when. They capture time – you can see the gaps when I went on holiday, or was busy delivering work. They remind me of the memories I have around those links – what was going on in my life at those points.
Anna goes through some of her favourite pattern libraries. It’s really, really great to see this stuff getting documented.
I met one of the guys from the Starbucks team at South by Southwest and he mentioned that they had a markup pattern library. I encouraged them to make it public, and it here it is!
I really hope that more companies and agencies will start sharing stuff like this.
It’s a blog. It’s a bookmark. It’s a magazine.
An in-depth look at naming patterns for classes to help streamline CSS.
Well, this looks clever: a self-updating bookmark (that’s an actual bookmark for books, not browsers).
An acid test for mobile browsers. Point your device at rng.io and it will report on how much or little mobile shininess is available.
Richard gives the lowdown on the new translate attribute in HTML.
A great pattern library from Dan.
A bookmarklet version of that handy multiple-iframe page I linked to the other day. Even more useful for testing responsive designs!
Some valuable musings from Ben on how browsers could be better — and I don’t mean the usual moaning about performance or device APIs.
A superb rallying cry from Mandy on the importance of markup literacy for professionals publishing on the web: writers, journalists, and most importantly, editors.
This is really handy: a bookmarklet that will disable any CSS3 on a page so you can check that your fallbacks look okay.
A really nice pattern for data tables in responsive designs. Just as with conditional loading, the key point is making a distinction between essential and optional content.
This helps to clarify the difference between native semantics and ARIA additions.
This is a great response to my recent post about semantics in HTML. Steve explores the accessibility implications. I heartily concur with his rallying cry at the end:
A very even-handed look at the time and data debacle in HTML5.
A single-serving website expressing the frustration and bewilderment at Hixie’s unilateral decision to drop the time element from HTML.
This is such a great idea: magnetic HTML elements. And now Cameron is sharing the source files so that we can all print our own.
Good design and good markup provide structure to content. Good markup is a fundamental part of good design: beautiful on the inside, beautiful on the outside. HTML and CSS give another venue to provide structure to content in the native language of the web, and learning these guides decisions by surfacing the affordances of the medium.
Insanely in-depth look at how browsers work, right down to the nitty gritty. You’d think there’d be a lot of engineering talk, but actually a lot of it is more about linguistics and language parsing.
A brave attempt to explain the new outline algorithm in HTML (although it inaccurately states that no browsers have support for it—Firefox shipped with it a while back).
You can safely skip the comments: most of them are discouraging, ignorant, and frankly, just plain stupid.
This is not as linkbaity as the title might suggest.
I’ve suggested the term “exploitationware” as a more accurate name for gamification’s true purpose…
A really nice little primer on getting started with HTML5.
Leonie points to a change in the semantics of the a element in HTML5 that could be very handy for accessible navigation.
A great round-up by Richard of some of the most common semantic pitfalls encountered with HTML5.
Everything you ever needed to know about adding HTML5 audio and video to your site, courtesy of the mighty John Allsopp.
A fascinating examination by Hixie of web technologies that may have technically been “better” than HTML, but still found themselves subsumed into the simpler, more straightforward, good ol’ hypertext markup language.
The follow-on comments are definitely worth a read too.
I agree 100% with Mark’s thoughts on what a Content Management System should and shouldn’t attempt to do.
I think that markup is too important to be left in the hands of the people who make content management systems. They all too often don’t care enough about it, and they can never know the context that you will be using it in, and so in my opinion they shouldn’t be trying to guess.
An excellent explanation from Richard of the bdi element (bi-directional isolate) for handling a mixture of left to right and right to left languages in HTML5.
I agree with Oli’s conclusion:
Steph Hay takes a look at how websites can allow a narrative to unfold, with the Ben The Bodyguard site as a case study.
A handy list of regular expressions that you can use in the new pattern attribute on the input element in HTML5.
Mike takes on the very tricky task of explaining the new outline algorithm—definitely one of the hardest features of HTML5 to explain, in my opinion.
A bookmarklet to help you figure out what files you might want to put in your cache manifest for offline storage.
I’m getting behind Oli’s proposal to allow non-quoted footers within blockquotes in HTML. Here’s where I quote the design principles to support his case.
An excellent article from Oli on markup patterns for quotations …though I still think that the cite element can be used for people’s names.
This could be handy for the editing process in my home-grown blogging system: a PHP script to convert HTML back to Markdown.
This dovetails nicely with my recent post about the spirit of distributed collaboration. Here’s a great little bit of near-history spelunking from Paul, all about styling new HTML5 elements in pesky older versions of Internet Explorer.
Buy. This. Book.
I mean it.
A good round-up by Jack Osborne of where things currently stand with the hgroup group.
Ben Buchanan has a nice round-up of some of the options available when you’re switching over to HTML5.
A handy bookmarklet that allows you to examine any piece of text on a website to determine what font it is set in.
An excellent statement of intent from Mark. You can either read this now and start creating websites the right way, or you can scrabble to catch up further down the line; I recommend reading this now.
Embrace the fluidity of the web. Design layouts and systems that can cope to whatever environment they may find themselves in. But the only way we can do any of this is to shed ways of thinking that have been shackles around our necks. They’re holding us back.
Start designing from the content out, rather than the canvas in.
A browser-based ePub reader. ‘Cause it’s (X)HTML all the way down, baby.
A nice succinct description of the placeholder attribute, with an emphasis on accessibility.
Some musings from Norman Walsh. I have to say, I’m still not entirely sure why the HTML/XML Task Force exists. The “use cases” described here are vague and handwavey.
A great round-up of some of the humbler new elements in HTML.
Good advice for generating markup with jQuery. As usual, there’s more than one way to do it.
A handy browser-based way of previewing the fonts installed on your computer.
A nice, neat, short introduction to microformats from Ben.
Paul has some further thoughts on self-hosting bookmarks while trying to retain the social aspect.
Bobbie is publishing the interviews he conducted with various HTML5 bods when he was researching his Technology Review article. First up: Hixie.
I firmly believe that this is very relevant to visual design on the web.
A quick run-through of some of the new HTML5 form features coming in Firefox 4.
Here's a little piece of web history: the proposal that was presented and rejected at the 2004 W3C workshop that led to the formation of the WHATWG.
A handy table of new HTML5 elements and whether or not they are exposed to assistive technology.
I couldn't agree more with this rant from Remy. He took the words right out of my mouth.
James Bridle propsed Open Bookmarks during a presentation at Tools of Change in Frankfurt today: "Open Bookmarks is not a thing, it’s a proposal, a flag in the ground. We need to agree on a way of sharing and storing annotations and bookmarks, reading attention data and everything around the book: that aura."
This might just be the best bookmarklet ever created. Use it to turn any page into an asteroid-like game of destruction.
A very handy page for showing HTML5 form element support in your browser.
Cute illustration of different content types in HTML (though, personally, I would put sectioning content — section, article, nav, aside — into their own group).
HTML5 resources, gathered together in one place.
A great post from the frontline of markup. This is just a taste of the confusion to come.
Another set of default HTML/CSS/JS templates with some very clever ideas built in (courtesy of the always-brilliant Paul Irish).
Barebones templates for HTML5 documents. It needs a bit of work but it's a nifty idea.
A great bit of research from Emily. She correctly values data more than opinion.
A wonderful document outlining the earliest history of the tags we know and love today.
An interesting performance proposal from mozilla that will degrade nicely in legacy browsers.
Making it up so you don't have to — somewhat like my New Media Company Name generator from a few years back.
An all-in-one validator from the W3C: markup, CSS and feed validation.