サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
ブックレビュー
adactio.com
Web components have been around for quite a while, but it feels like they’re having a bit of a moment right now. It turns out that the best selling point for web components was “wait and see.” For everyone who didn’t see the benefit of web components over being locked into a specific framework, time is proving to be a great teacher. It’s not just that web components are portable. They’re also web
I received this email recently: Subject: multi-page web apps Hi Jeremy, lately I’ve been following you through videos and texts and I’m curious as to why you advocate the use of multi-page web apps and not single-page ones. Perhaps you can refer me to some sources where your position and reasoning is evident? Here’s the response I sent… Hi, You can find a lot of my reasoning laid out in this (shor
When I talk about evaluating technology for front-end development, I like to draw a distinction between two categories of technology. On the one hand, you’ve got the raw materials of the web: HTML, CSS, and JavaScript. This is what users will ultimately interact with. On the other hand, you’ve got all the tools and technologies that help you produce the HTML, CSS, and JavaScript: pre-processors, p
Ethan quite rightly points out some semantic sleight of hand by Google’s AMP team: But when I hear AMP described as an open, community-led project, it strikes me as incredibly problematic, and more than a little troubling. AMP is, I think, best described as nominally open-source. It’s a corporate-led product initiative built with, and distributed on, open web technologies. But so what, right? Tom-
AMP Conf was one of those deep dive events, with two days dedicated to one single technology: AMP. Except AMP isn’t really one technology, is it? And therein lies the confusion. This was at the heart of the panel I was on. When we talk about AMP, we could be talking about one of three things: The AMP format. A bunch of web components. For instance, instead of using an img element on an AMP page, y
There were plenty of talks about building for the web at this year’s Google I/O event. That makes a nice change from previous years when the web barely got a look in and you’d be forgiven for thinking that Google I/O was an event for Android app developers. This year’s event showed just how big Google is, and how it doesn’t have one party line when it comes to the web and native. At the same time
When something on your website is shared on Twitter or Facebook, you probably want a nice preview to appear with it, right? For Twitter, you can use Twitter cards—a collection of meta elements you place in the head of your document. For Facebook, you can use the grandiosely-titled Open Graph protocol—a collection of meta elements you place in the head of your document. What’s that you say? They so
I’ve made no secret of the fact that I’m really excited about Service Workers. I’m not alone. At the Coldfront conference in Copenhagen, pretty much every talk mentioned Service Workers. Obviously I’m excited about what Service Workers enable: offline caching, background processes, push notifications, and all sorts of other goodies that allow the web to compete with native. But more than that, I’m
Bruce has written a great article called On the accessibility of web components. Again. In it, he takes issue with the tone of a recent presentation on web components, wherein Dimitri Glazkov declares: Custom elements is really neat. It basically says, “HTML it’s been a pleasure”. Bruce paraphrases this as: Bye-bye HTML; you weren’t useful enough. Hello, brave new world of custom elements. Like Br
There’s been quite a brouhaha over the past couple of days around the subject of standardising responsive images. There are two different matters here: the process and the technical details. I’d like to address both of them. Ill communication First of all, there’s a number of very smart developers who feel that they’ve been sidelined by the WHATWG. Tim has put together a timeline of what happened:
I got some great comments on my post about conditionally loading content. Just to recap, I was looking for a way of detecting from JavaScript whether media queries have been executed in CSS without duplicating my breakpoints. That bit is important: I’m not looking for MatchMedia, which involves making media queries in JavaScript. Instead I’m looking for some otherwise-useless CSS property that I c
When I met up with Malarkey right before An Event Apart in Seattle he told me about a quick bit of guerrilla testing he had been doing. He popped into a store selling Windows Phone 7 devices and started surfing the web. Specifically, he started looking at sites using responsive design like Jon’s and Colly’s. Most of the sites he looked at displayed the desktop layout instead of adapting to the sma
Over on the HTML5 Doctor site, Oli has written a great article called Quoting and citing with <blockquote>, <q>, <cite>, and the cite attribute. Now, I still stand by my criticism of the way the cite element has been restrictively redefined in HTML5 such that it’s not supposed to be used for marking up a resource if that resource is a person. But I think that Oli has done a great job in setting ou
Hashbangs. Yes, again. This is important, dammit! When the topic first surfaced, prompted by Mike’s post on the subject, there was a lot of discussion. For a great impartial round-up, I highly recommend two posts by James Aylett: Wisdom comes from genuine reflection and Client-side routing, the teenage years. There seems to be a general concensus that hashbang URLs are bad. Even those defending th
I remember when Google Maps first launched back in February 2005. As well as being enormous fun—I spent hours finding famous landmarks and places—it was a complete game-changer. The “slippy maps” style of interaction felt weird, then delightful and then just …right. Things move fast on the web. It didn’t take long for us to get used to slippy maps. Before too long, we came to expect them. These da
The Design of HTML5 October 18th, 2010 The opening keynote from Fronteers 2010 in Amsterdam. Watch the video of this talk. Download the slides. I would like to talk to you today about The Design of HTML5. So there’s two parts to this: one is, of course, HTML5. I could stand up here and just talk about HTML5 but that’s not what I’m going to do because if you want to know what is in HTML5 you can Go
I went along to the fifth Barcamp Brighton on the weekend. It was a truly excellent event, hosted in The Skiff, a great coworking space. Alas, a creeping cold meant that I couldn’t stick around for too long, but I made sure to give a presentation before I bailed. I spoke about media queries. As you may have gathered from my recent entries, this is something I’ve been thinking about a lot lately. I
Ideally, the table would show a nice uniform graph: a solid diagonal line from the top left left to the bottom right. The diagonal line is there but it isn’t exactly uniform. For the record, here are the element names together with their correct definitions. I’ve included a little sparkline with each one to show the distribution of answers. A unanimous result would show one clear spike. Wobbly une
<!DOCTYPE html> Specification whatwg.org/html5 Mailing lists whatwg.org/mailing-list IRC channel irc://irc.freenode.org/whatwg article A composition that forms an independent part of a document, page, application, or site. aside Content that is tangentially related to the content around the aside element nav A section with navigation links. section A generic document or application section. h1, h2
I can never pinpoint the exact moment at which I “get into” a particular technology. CSS, DOM Scripting, microformats …there was never any Damascene conversion to any of them. Instead, I’d just notice one day, after gradually using the technology more and more, that I was immersed in it. That’s how I feel about HTML5 now. There’s another feeling that accompanies this realisation. I remember feelin
Eric Meyer is going to talk about CSS frameworks here at An Event Apart San Francisco. He did a Google search for “CSS Frameworks” and put together a list of the big players. It’s a list of nine frameworks. Eric wants to know two things: what are they doing the same and what are they doing differently. 960 Blueprint Content With Style That Standards Guy YAML YUI Elements Tripoli WYMStyle Let’s get
Using DOM Scripting to Plug the Holes in CSS July 13th, 2006 A talk I gave at @media 2006 in London. Listen to the original audio recording. View the presentation slides Jeremy Keith: Can everyone hear me ok? Is this on? Is everyone reading me correctly? Okay, then I think, I think we’ll dive right in. Good morning. Thank you all very much for coming to the techy one instead of the designery one.
Making websites. Writing books. Hosting a podcast. Speaking at events. Living in Brighton. Working at Clearleft. Playing music. Taking photos. Answering email. The invisible seafaring industry that keeps the internet afloat A fascinating in-depth look at the maintenance of undersea cables: The industry responsible for this crucial work traces its origins back far beyond the internet, past even the
The Behaviour Layer: Using JavaScript for good, not evil
このページを最初にブックマークしてみませんか?
『Adactio: Jeremy Keith』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く