added 2007 Sat Nov 24 7:00:00 by unknown user
A must read article on A List Apart, by Jeffrey Zeldman: "If not everyone appreciates this beauty?if not everyone understands web design?then let us not cry for web design, but for those who cannot see." Saved By: Emilio Vanni | View Details | Give Thanks
A must read article on A List Apart, by Jeffrey Zeldman: "If not everyone appreciates this beauty?if not everyone understands web design?then let us not cry for web design, but for those who cannot see." Saved By: Emilio Vanni | View Details | Give Thanks
added 2007 Tue Nov 20 7:00:00 by unknown user
A must read article on A List Apart, by Jeffrey Zeldman: "If not everyone appreciates this beauty?if not everyone understands web design?then let us not cry for web design, but for those who cannot see." Saved By: Emilio Vanni | View Details | Give Thanks
A must read article on A List Apart, by Jeffrey Zeldman: "If not everyone appreciates this beauty?if not everyone understands web design?then let us not cry for web design, but for those who cannot see." Saved By: Emilio Vanni | View Details | Give Thanks
A List Apart: Setting Type on the Web to a Baseline Grid
ma.gnolia tags : web 2.0 twitter social social bookmarking cars distance fuel webapp travel voyage tools Domains smashing-magazine i n f o architecture visualisation imported time magazine gary vaynerchuk wine library tv wltv jasonkottke facebook aol api system:unfiled cms opensource php photos list overview online iphone sdk webdev resources Diigo - Thaneshkumar's Bookmarks larissameek Design webdesign ssl tls web Security mac apps ssh ftp javascript mootools Fan fiction images writing effects library free alistapart wilsonminer typography
added 2007 Fri Jun 29 7:00:00 by unknown user
Wilson Miner's first A List Apart article has been posted, just in time for me to cop all the ideas for use in my upcoming workshop on web typography in London. Wilson's been working on this for quite some time, and it shows. The topic -- aligning text to a baseline grid -- is something I've been working on a lot myself lately. It's not quite as simple on the web as it ought to be, but Wilson shows you how it can be done with the minimal amount of pain. And the result -- well, the result is just a *much* more professional-looking page. It really makes a big difference. Wilson ends the article with a note on sizing text in pixels, which bring me to a slightly related topic. Did you know you can actually resize text set in pixels with IE6? Yup, you can. You can have turn on the "Ignore font sizes..." option in the accessibility dialog, but it can be done. This led me to wonder (again) how much responsibility should fall on users (especially those with unique needs) to learn their tools. In a comment on [Roger's site](http://www.456bereastreet.com/archive/200703/ie_7_does_not_resize_text_sized_in_pixels/#comment77), I said this: > I have neck and back problems, myself. Because of that, I have to buy a decent chair and take the time to configure it for the optimal support. If I don't, I'll end up in pain when I'm reading a book at my desk. If I choose to sit in a crappy chair, or I choose not to configure my chair the way that is best for me, or I simply don't learn how my chair works -- whose fault is that? I'd say it's my fault. You can maybe make an argument that it's the chair manufacturer's fault, because they didn't make it easy enough for me to use my chair properly. But I don't see any way in hell you can blame it on the book I'm reading. Do you? Go read Wilson's article. It's really great.
Wilson Miner's first A List Apart article has been posted, just in time for me to cop all the ideas for use in my upcoming workshop on web typography in London. Wilson's been working on this for quite some time, and it shows. The topic -- aligning text to a baseline grid -- is something I've been working on a lot myself lately. It's not quite as simple on the web as it ought to be, but Wilson shows you how it can be done with the minimal amount of pain. And the result -- well, the result is just a *much* more professional-looking page. It really makes a big difference. Wilson ends the article with a note on sizing text in pixels, which bring me to a slightly related topic. Did you know you can actually resize text set in pixels with IE6? Yup, you can. You can have turn on the "Ignore font sizes..." option in the accessibility dialog, but it can be done. This led me to wonder (again) how much responsibility should fall on users (especially those with unique needs) to learn their tools. In a comment on [Roger's site](http://www.456bereastreet.com/archive/200703/ie_7_does_not_resize_text_sized_in_pixels/#comment77), I said this: > I have neck and back problems, myself. Because of that, I have to buy a decent chair and take the time to configure it for the optimal support. If I don't, I'll end up in pain when I'm reading a book at my desk. If I choose to sit in a crappy chair, or I choose not to configure my chair the way that is best for me, or I simply don't learn how my chair works -- whose fault is that? I'd say it's my fault. You can maybe make an argument that it's the chair manufacturer's fault, because they didn't make it easy enough for me to use my chair properly. But I don't see any way in hell you can blame it on the book I'm reading. Do you? Go read Wilson's article. It's really great.
A List Apart: Frameworks for Designers, by me!
ma.gnolia tags : larissameek Design webdesign dev mha safari Apple Programming css reference templates icons&patterns&images Essential HTML javascript php free fonts typography email html tabs Navigation google analytics website apache cheatsheet webdev type danse ma.gnolia wordpress feedblendr magpierss alistapart jeffcroft ego
added 2007 Tue Jun 12 7:00:00 by unknown user
I wrote a shot piece for A List Apart on how the concept of frameworks can apply to designers, and specifically to CSS. We hear about frameworks all the time these days, but the concept is usually relegated to programmers doing JavaScript or server-side scripting. It turns out a good set of abstracted CSS idioms can also be very effective in speeding up your web design process.
I wrote a shot piece for A List Apart on how the concept of frameworks can apply to designers, and specifically to CSS. We hear about frameworks all the time these days, but the concept is usually relegated to programmers doing JavaScript or server-side scripting. It turns out a good set of abstracted CSS idioms can also be very effective in speeding up your web design process.
A List Apart: Setting Type on the Web to a Baseline Grid
ma.gnolia tags : resources code css layout tips system:unfiled webdev type typography tool web design alistapart wilsonminer webdesign
added 2007 Sat Apr 14 7:00:00 by unknown user
Wilson Miner's first A List Apart article has been posted, just in time for me to cop all the ideas for use in my upcoming workshop on web typography in London. Wilson's been working on this for quite some time, and it shows. The topic -- aligning text to a baseline grid -- is something I've been working on a lot myself lately. It's not quite as simple on the web as it ought to be, but Wilson shows you how it can be done with the minimal amount of pain. And the result -- well, the result is just a *much* more professional-looking page. It really makes a big difference. Wilson ends the article with a note on sizing text in pixels, which bring me to a slightly related topic. Did you know you can actually resize text set in pixels with IE6? Yup, you can. You can have turn on the "Ignore font sizes..." option in the accessibility dialog, but it can be done. This led me to wonder (again) how much responsibility should fall on users (especially those with unique needs) to learn their tools. In a comment on [Roger's site](http://www.456bereastreet.com/archive/200703/ie_7_does_not_resize_text_sized_in_pixels/#comment77), I said this: > I have neck and back problems, myself. Because of that, I have to buy a decent chair and take the time to configure it for the optimal support. If I don't, I'll end up in pain when I'm reading a book at my desk. If I choose to sit in a crappy chair, or I choose not to configure my chair the way that is best for me, or I simply don't learn how my chair works -- whose fault is that? I'd say it's my fault. You can maybe make an argument that it's the chair manufacturer's fault, because they didn't make it easy enough for me to use my chair properly. But I don't see any way in hell you can blame it on the book I'm reading. Do you? Go read Wilson's article. It's really great.
Wilson Miner's first A List Apart article has been posted, just in time for me to cop all the ideas for use in my upcoming workshop on web typography in London. Wilson's been working on this for quite some time, and it shows. The topic -- aligning text to a baseline grid -- is something I've been working on a lot myself lately. It's not quite as simple on the web as it ought to be, but Wilson shows you how it can be done with the minimal amount of pain. And the result -- well, the result is just a *much* more professional-looking page. It really makes a big difference. Wilson ends the article with a note on sizing text in pixels, which bring me to a slightly related topic. Did you know you can actually resize text set in pixels with IE6? Yup, you can. You can have turn on the "Ignore font sizes..." option in the accessibility dialog, but it can be done. This led me to wonder (again) how much responsibility should fall on users (especially those with unique needs) to learn their tools. In a comment on [Roger's site](http://www.456bereastreet.com/archive/200703/ie_7_does_not_resize_text_sized_in_pixels/#comment77), I said this: > I have neck and back problems, myself. Because of that, I have to buy a decent chair and take the time to configure it for the optimal support. If I don't, I'll end up in pain when I'm reading a book at my desk. If I choose to sit in a crappy chair, or I choose not to configure my chair the way that is best for me, or I simply don't learn how my chair works -- whose fault is that? I'd say it's my fault. You can maybe make an argument that it's the chair manufacturer's fault, because they didn't make it easy enough for me to use my chair properly. But I don't see any way in hell you can blame it on the book I'm reading. Do you? Go read Wilson's article. It's really great.
A List Apart: Ruining the User Experience
ma.gnolia tags : web 2.0 web design web design tools javascript web development css mac productivity tips tutorials tutorial Design colour theory resources tribal ethnic tibetanjewelry jewelry pagerank alexa stats girls clothing children clothes portfolio web2.0 wiki wissensmanagement socialsoftware Internet culture social software psychology Windows share rounded corners safety passwords aarongustafson webprogramming alistapart
added 2007 Wed Mar 28 7:00:00 by unknown user
Aaron Gustafson (who is a helluva nice guy, and super smart to boot) has a nice piece on ALA which deals largely with sites that require JavaScript. Aaron seems to advocate that one should never *require* JavaScript in their web app, but rather use it only as an enhancement to improve the UI for that visitors with JavaScript enabled (and this, coming from a JavaScript guy). I don't quite agree with Aaron here. I believe there are cases where it's fair to require JavaScript in a web app. We make all kinds of techniqual requirements for desktop apps (you must have *x* amount of RAM, you must have such-and-such video card, etc.) , and I don't see why it should be any different online. That having been said, we should only make these requirements in cases where the app simply isn't possible with them -- which is definitely *not* the case in the examples Aaron uses in the article. Overall, I agree with the sentiment that we should always try to make our apps work without JavaScript. But, I also think there are cases where that simply isn't possible.
Aaron Gustafson (who is a helluva nice guy, and super smart to boot) has a nice piece on ALA which deals largely with sites that require JavaScript. Aaron seems to advocate that one should never *require* JavaScript in their web app, but rather use it only as an enhancement to improve the UI for that visitors with JavaScript enabled (and this, coming from a JavaScript guy). I don't quite agree with Aaron here. I believe there are cases where it's fair to require JavaScript in a web app. We make all kinds of techniqual requirements for desktop apps (you must have *x* amount of RAM, you must have such-and-such video card, etc.) , and I don't see why it should be any different online. That having been said, we should only make these requirements in cases where the app simply isn't possible with them -- which is definitely *not* the case in the examples Aaron uses in the article. Overall, I agree with the sentiment that we should always try to make our apps work without JavaScript. But, I also think there are cases where that simply isn't possible.
Ethan on ALA: Where Our Standards Went Wrong
ma.gnolia tags : None assigned openid whitelisting django code web development .programme Linux english&writing writing language poetry logo design Design web2.0 glossary ajax css javascript resume rands tech dictionnary rss no_tag mac screensaver imported Website Creation Resources templates ethanmarcotte alistapart webdesign webstandards
added 2007 Tue Feb 27 7:00:00 by unknown user
A *great* article by Ethan Marcotte on how we need to redefine the message we use in web standards evangelism. He touches on two things that baffle my mind. First, I don't understand why anyone would ever validate someone else's code and then speak publicly about the errors they find. If you do that, you're being an asshole. Period. Validation is a process for you to do on *your code*, so as to help you avoid the timesink that is working with broken code later -- using invalid code will especially kill you when you go to add DOM scripting or CSS to the page. Don't validate other people's code. It's assholish. Second, he mentions how some CMSes are still spewing tag-soup all over our web. I find this, frankly, absurd. If your CMS that doesn't allow you 100%, full control over its output via a template system of some sort, you've got to find a way off of that thing. Any CMS that doesn't give you full control of the output is not worth anyone's time.
A *great* article by Ethan Marcotte on how we need to redefine the message we use in web standards evangelism. He touches on two things that baffle my mind. First, I don't understand why anyone would ever validate someone else's code and then speak publicly about the errors they find. If you do that, you're being an asshole. Period. Validation is a process for you to do on *your code*, so as to help you avoid the timesink that is working with broken code later -- using invalid code will especially kill you when you go to add DOM scripting or CSS to the page. Don't validate other people's code. It's assholish. Second, he mentions how some CMSes are still spewing tag-soup all over our web. I find this, frankly, absurd. If your CMS that doesn't allow you 100%, full control over its output via a template system of some sort, you've got to find a way off of that thing. Any CMS that doesn't give you full control of the output is not worth anyone's time.
A List Apart: Flash Embedding Cage Match
ma.gnolia tags : css holy grail multi-column layout photography web design graphic design portfolios conversor marketing research knowledge pricing business freeware Apple mac photo javascript photogallery everquest tips cheats codes hints world of warcraft video game play listen to xena battle cry everquest thurgadin adobe illustrator tutorials graphics list reference Design imported simonwillison django webprogramming urls im furniture Video cool tip(s) Programming web macosx vim Software cocoa quicktime recording tool(s) nft webdev bookmarklets 2do flash webstandards alistapart webdesign
added 2007 Tue Feb 6 7:00:00 by unknown user
There are approximately 1,342,973 different methods for embedding you SWF files in (X)HTML pages. Ask web-standards oriented developers which is best, and you'll get approximately 1,342,974 answers. This article does a nice job of breaking down the differences between the most popular methods.
There are approximately 1,342,973 different methods for embedding you SWF files in (X)HTML pages. Ask web-standards oriented developers which is best, and you'll get approximately 1,342,974 answers. This article does a nice job of breaking down the differences between the most popular methods.
A List Apart: Your About Page Is a Robot
ma.gnolia tags : css tools font preview ico png icone "language learning" javascript rails ruby rubyonrails torrent search downloads travel:fares imported macware freeware 2do graphics charts lists web Internet website Design fun tool(s) socialnetwork(s) logo banner creator generator photography community illustration artist online free pdf colour colour blind erinkissane alistapart writing
added 2006 Tue Aug 22 7:00:00 by jcroft
A cute, fun, and oh-so-true little article by Erin Kissane on the state of about pages on the web today -- and, of course, how to make yours suck less.
A cute, fun, and oh-so-true little article by Erin Kissane on the state of about pages on the web today -- and, of course, how to make yours suck less.
