What is it?

rel="logo" is a proposed standard for serving and maintaining up-to-date logos for use in various media. By including a line of code on your site that links to a scalable vector logo, you make it very easy for other websites, applications, readers, clients, and stations to ensure that they are using an approved logo directly from you.

rel="logo" is a link relation tag, much like commonly used icon tags favicon or apple-touch-icon.

QueryPath is a PHP library for manipulating XML and HTML. It is designed to work not only with local files, but also with web services and database resources. It implements much of the jQuery interface, but it is heavily tuned for server-side use.

Do you want a 3 KB cross-browser native JavaScript that makes your plain HTML lists super flexible, searchable, sortable and filterable? Yeah!
Do you also want the possibility to add, edit and remove items by dead simple templating? Hell yeah!

One of my least favorite parts about layout with CSS is the relationship of width and padding. You're busy defining widths to match your grid or general column proportions, then down the line you start to add in text, which necessitates defining padding for those boxes. And 'lo and behold, you now are subtracting pixels from your original width so the box doesn't expand.

Ugh. If I say the width is 200px, gosh darn it, it's gonna be a 200px wide box even if I have 20px of padding. So as you know, this is NOT how the box model has worked for the past ten years. Wikipedia has a great history of this box model.

Anyway, I have a recommendation for your CSS going forward:

/* apply a natural box layout model to all elements */
* { -moz-box-sizing: border-box; -webkit-box-sizing: border-box; box-sizing: border-box; }
This gives you the box model you want. Applies it to all elements. Turns out many browsers already use border-box for a lot of form elements (which is why inputs and textareas look diff at width:100%;) But applying this to all elements is safe and wise.

Pears are common patterns of markup & style.

Pears is an open source WordPress theme. I'll admit the code
is a bit rough, initially based on the default 'twentyone' theme.

I wanted a handy way of collecting HTML & CSS pattern pairs.
Often used modules with a minimal of style applied. It's become
a valuable learning tool, whereby breaking interfaces down into
small pieces make it easier to learn and improve running code.

Learn more and see it in action here:
http://pea.rs

I haven’t done serious web work — HTML web work, that is — since I last worked on Manila 10 years ago.

I’ve done some small things — the system that generates this blog, for instance — but I haven’t had the chance to use almost any of the newer web technology. I’ve never written a Rails app, used JQuery, or deployed to a virtual server.

So when I had the chance to re-do the websites for our company and main product, I was excited — because it meant I could try some of the new technologies and learn some things.

Sectioning content elements and friends

I’ve been recently working on optimizing performance of a so-called one-page web app. The application was highly dynamic, interactive, and was heavily stuffed with new CSS3 goodness. I’m not talking just border-radius and gradients. It was a full stack of shadows, gradients, transforms, sprinkled with transitions, smooth half-transparent colors, clever pseudo-element -based CSS tricks, and experimental CSS features.

Aside from looking into bottlenecks on Javascript/DOM side, I decided to step into the CSS land. I wanted to see the kind of impact these nice UI elements have on performance. The old version of the app — the one without all the fluff — was much snappier, even though the JS logic behind it hasn’t changed all that drastically. I could see by scrolling and animations that things are just not as quick as they should be.

Was styling to blame?

Fortunately, just few days before, Opera folks came out with an experimental “style profiler” (followed by WebKit’s ticket+patch shortly after). The profiler was meant to reveal the performance of CSS selector matching, document reflow, repaint, and even document and css parsing times.

This is a list of best practices for creating websites that do not break when browsers are updated. It's not always possible to follow all of these, but following as many of them as possible will help future-proof your website. This is especially important for intranet applications and other non-public websites where problems are likely to not be noticed during testing by browser vendors.

Tempo is a tiny JSON rendering engine that enables you to craft data templates in pure HTML.

Why use Tempo?
Clear separation of concerns: no HTML in your JavaScript files
It makes AJAX content easier to work with
It's as friendly as a bunny rabbit (which are quite friendly)

Key Features
Works in Safari, Chrome, FireFox, Opera, and Internet Explorer 6+
Itty-bitty footprint, lightning-fast rendering!
No dependencies - Works with or without jQuery
Degrades gracefully if JavaScript is not enabled
Supports nested and conditional templates

HTML5 is the new kid on the block, sure, and with reports that an official specification wont be fully completed and officially supported until 2022, you may be wondering why you should use it in your new site.

Well, there's one main reason (for me at least), and that is: The Future. The simple fact is that HTML4/XHTML1.0/CSS2 are outdated, and the new XHTML 2 standard has been scrapped in favor of HTML5. CSS3 is gaining more and more momentum every single day, the future of the web is HTML5.

We are passionate about the web, learning, and craftsmanship. We want you, as web designers and developers, to be successful in your careers. We feel, though, that W3Schools is harming the community with inaccurate information. Like any other authoritative educational resource, W3Schools should both hold itself to, and be held to, the highest standards.

We hope we can illuminate why W3Schools is a troublesome resource, why their faulty information is a detriment to the web, and what you (and they) can do about it.

I am widely credited as the inventor of the <blink> tag.   For those of you who are relatively new to the Web, the <blink> tag is an HTML command that causes text to blink, and many, many people find its behavior to be extremely annoying.    I won't deny the invention, but there is a bit more to the story than is widely known.

Within the last few months — though I’d been intending to do so for much longer than that — I made the decision to switch all my client work starting point templates from XHTML over to HTML 4.01 and start delivering everything as plain old semantic HTML, minus the X.

En enkelt och smidigt sätt att bygga forumlär på nätet, går att koppla till paypal-betalning också.

En smart och bra färgväljare i javascript för webbsidor.

En artikel om en funktion att representera en webbsajt som en grafiskt träd över HTML DOM:en, dvs tagg-strukturen.

Sitepoint om hur man kodar HTML-mejl på bästa sätt.

Artikel om hur säkerhetsproblem när man tillåter stil och anpassning i koden.

En guide över vad som fungerar när det gäller CSS i HTML-mejl.

HTML_AJAX är ett PEAR package för att göra AJAX-operationer för PHP

En artikel om hur "specificity" fungerar i CSS, dvs hur olika stilinformationen styr över det slutgiltiga utseendet.

Digital Web Magazine har en artikelserie om CSS, grundläggande CSS. Detta är del 1.

Digital Web Magazine har en artikelserie om CSS, grundläggande CSS. Detta är del 1.

Hur man jobbar med användarvänlighet (usability) för XMLHttpRequest i praktiken.

En guide för hur man jobbar med CSS på ett strukturerat sätt. Först tänker man struktur, sen layout. Tvärt emot hur man gjorde när man använde HTML för presentationen.

En steg-för-steg-genomgång av hur man gör en sajtdesign med bra CSS- och HTML-kod. Många bra tips och idéer.

Hur man bäddar in FlashObjects, flash-filmer, på bästa sätt.

En toolkit för att använda Ajax (XMLHttpRequest mm) från PHP.

En artikel hos XML.com om hur man använder XMLHttpRequest, men förklaringar och exempel.

En dissektion av Google Maps som använder avancerad webbteknik för att leverera sitt resultat.

En mycket intressant WYSIWYG-editor i klass med FCKedit.

En Slashdot-tråd om hur Google Suggest fungerar. Väldigt smart och innovativt!

En bra sammanfattning av hur man citerar i HTML av Roger Johansson (456 Berea Street).

En artikel från Apple om bästa sättet att utveckla webbsidor.

En lista över vilka symboler (och grekiska bokstäver) som finns i HTML 4.0.