Why Wait Webs

Why Wait Webs indexed on first page of Google thanks to having search-engine friendly content.

We have all seen websites, books, and seminars dedicated to one of today’s hottest topics: search-engine optimization. There is a lot of information out there, a lot of it helpful, and a lot of it completely bogus or largely fluff. If you are new to the subject of SEO, the plethora of information available about writing content for search engines can be quite daunting.

Fortunately when it comes right down to it, one of the most consistent, tried and true methods of search engine optimization is simply writing search-engine friendly content, which is something anyone can do if they follow a couple very simple techniques. By the end of this short article, you should be able to write search-engine friendly content that will allow your website to get indexed by Google and the other search engines much more effectively.

[click here to read the rest of the article]

I don’t like Internet Explorer. I don’t think I’ve made that any secret. One of the reasons for that is that there are many instances where fully valid code won’t render properly in IE6 — many more instances than is the case with other browsers.

IE6 Showing its True Malevolent Self

Today I found the strangest and most terrible bug I’ve ever encountered. In Internet Explorer 6, my main content was completely invisible. Images and text alike were simply gone! The container DIV was stretched out as it would be if the content were there, and the text was selectable! If I highlighted the text, in fact, I was able to see it, even after de-selecting it. On a page refresh however, my content would simply disappear again, only to reappear when highlighted.

I consider this the most terrible bug ever because in most cases, a bug will rearrange your website, or make it look ugly, but users will still be able to access the content. The content is the reason for the site’s existence, and with this disappearing content bug, users of Internet Explorer 6 will not see your content unless they think to highlight it (and in that particular demographic, I’m willing to bet the odds of that are pretty low). Thus your entire site is rendered unusable and pointless. So read on for the fix!

[click here to read the rest of the article]

WordPress 2.7 recently came out. For those of you who don’t know, WordPress is the most popular blogging platform in the world, and deservedly so. It is highly customizable and extremely themeable. It’s coded with standard, valid XHTML and CSS. My only real complaint with WordPress is that they, like much of the web, chose to use XHTML instead of HTML when there’s no real reason for it. But that’s a topic for another day. As it stands, WordPress is still the best CMS I’ve ever used by far, and that’s why I use it on my own site and recommend it to all of my clients.

I am going to be upgrading this blog and, if all goes well, my clients’ blogs shortly thereafter. Normally I wouldn’t go to the trouble of updating, but this is a big one. Instead of the usual one or two obscure bug fixes, the WP team has completely redesigned the back-end, and from what I’ve seen they’ve done a really good job of turning a great blogging platform into a truly rich CMS (content management system).

Continue reading to find out what some of these great new features are, and for a video showcasing them!

[click here to read the rest of the article]

Apple, developer of Mac OS X

Ok, it’s true. I am a big fan of Apple products. I do most of my work on a 24 inch iMac, and I find myself using my iPhone constantly throughout the day. I like these products because I’ve tried the alternatives, and I have found that for me, these are by far the best solutions. However, even though I’m a fan of Macs, I would never condone a website that doesn’t support PCs. I believe that right now, there is no reason why EVERYTHING computers can do shouldn’t be done cross-platform. That means OS X, and even Linux.

You see, applications and websites that are built from the ground up with these smaller platforms in mind don’t take any extra effort. Supporting an extra 12% or so of the market is easy to do, but yet so few developers do it. I came across an excellent article today about why game developers should support Mac OS X and Linux. But the concept extends beyond just game developers. Software developers of any kind, including website developers, should take heed to this information. Continue reading to see why.

[click here to read the rest of the article]

With Safari now hovering around 8% of browser market share, it is important that web developers and designers test it almost as thoroughly as they would Firefox. Although the numbers don’t lie, plenty of developers/designers still don’t test Safari at all. Even those who do are easily prone to missing this one, as it’s rather difficult to see on lackluster monitors. There is a little-known issue in Safari where color in images mismatches with the CSS background colors. I won’t pretend to know the nitty-gritty details of how this works, but essentially Webkit renders CSS hex codes slightly different than it renders image colors.

Safari Background Image-Color Mismatch

Normally this background image/color mismatch is not noticeable enough to be a problem. However, if you are trying to fake transparency, and part of your image is meant to look like the background, the image/css color profile difference becomes immediately visible on modern monitors, since the background image intended to blend with the CSS solid color does not quite match up. This is shown in the image to the left, but again, you have to have a nice and bright monitor to see it. In case you’re having trouble seeing it, I highlighted the edges of the image, where the gray varies slightly, in the second image below and to the right.

[click here to read the rest of the article]