You will probably find a design principle or multiple design principles behind all good examples of anything that has been built collaboratively.
#Download keynote 2010 software#
It doesn’t matter wether your making a specification or if you are making a physical object or a piece of software or a programming language. Design principlesĪ design principle is essentially a belief, a tenant, a concept that you rally behind. Design principles are something I am getting more and more fascinated with. In particular, one of the reasons why I think HTML5 as a specification is quite successful-and the process has been successful-is that it is driven by design principles. What I want to talk about is not so much what is in the spec but why these things are in the spec, what the process was in thinking of these things when designing a specification. It’s the other side of it, it’s the design of HTML5. It’s not going through a checklist of what’s in HTML5. I’m specifically talking about the specification: HTML5.Īs I said, it’s not so much the contents I want to talk about. I don’t mean this umbrella term that covers anything that’s new these days. It’s supposed to mean a specific specification and now it just means “doing anything cool (fullstop) on the web.” But that’s not the HTML5 I mean. It used to be that Ajax meant something specific and then, after a while, it just became “doing anything cool with Javascript.” That was Ajax, right? And now the same thing seems to be happening to the term HTML5. When I say HTML5 I don’t mean CSS3, I mean HTML5. For example, referring to CSS3 as HTML5 for some reason seems to be a common technique. The problem is other people are using the term HTML5 to refer to just about anything, which can be problematic. So I’m not just going to stand up here and run through what’s in HTML5.Īctually, before I even get started I should probably clarify what I mean by HTML5, which seems kind of crazy ‘cause why should I have to clarify what I mean by HTML5 when what I mean by HTML5 is HTML5? There’s a specification, it’s called HTML5 and when I say HTML5 that’s what I am referring to. Paul Irish is going to go through a whole bunch of the APIs that are in HTML5.
Steve Faulkner will be talking about accessibility and 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 Google it, you can read books, you can go and read the spec.Īctually, some other people are going to be talking about the contents of the spec. So there’s two parts to this: one is, of course, HTML5. I would like to talk to you today about The Design of HTML5.
0 kommentar(er)
