LevelTen In-Site Blog
left shadow

Archive for May, 2006

May 18th, 2006
Posted by Neil at 4:48 pm

Premise:

As shoppers are becoming more sophisticated in e-browsing and e-shopping, product search engines, verses general search engines, are quickly becoming a large source for product and online store recommendations. This blog entry covers a strategic method of benefiting from other companies’ product search engine marketing efforts, adding yet another element to the online product marketing mix: Search Engine Merchandising & Pay-per-click Piggy Backing.

E-Commerce Dream Dashing

An excited client comes to your web company with a gleaming dot com product-selling dream and dollar signs in his or her eyes, wanting an online store selling products which, in their mind, will cut back on the common hassles of a brick-and-mortar store.

How do you explain to your new client that their website could have poor placement in Google for their primary keywords for up to a year or more? How does one make these eager entrepreneurs understand that Google, and Yahoo! to a lesser degree, has a “time out” period, or “sandbox,” before it allows new sites in the search listings?

Read the rest of this entry »

Category: Web Strategy, Internet Marketing

divider
Posted by Matt at 3:38 pm

colorpix.gifI actually forgot what lead me to Color Schemer this morning, but the discovery of sweet, inexpensive little apps is always a nice way to start the day. While I haven't dowloaded the full version yet, I have been using the FREE ColorPix app (pictured) for several hours. It functions a lot like ColorZilla, but with some bonuses:

  1. It deciphers color from anywhere on your screen. So unlike CZ, you're not restricted to your web browser.
  2. It's magnifying tool allows you to select a color and then click on the information display to copy the RGB, HEX, HSB and/or CMYK values to your clipboard. (Note: ctrl+click on the HEX value to copy it without the # symbol.)
  3. You can set the preferences to launch the app when windows starts up … ooooh stinker - I just realized it's only available for Windows. Sorry MACophiles - you'll have to drop a Grant (Ulysses S., that is) and purchase the whole shabang. At the moment, I'm getting out of debt and can't afford such frivolities.

What makes this little puppy so appealing to me isn't so much it's functionality as it's community of users. Color Schemer is drawing a bit of a crowd - and a talented one at that. The forums section of their website is repleat with tips, advice and shop-talk. I'm a little gitty over the color scheme gallery. It showcases loads of fantastic schemes for untalented hacks like myself to download and apply.

Category: General Thoughts

divider
May 9th, 2006
Posted by Chris Ruppel at 1:37 pm

Note: this is intended for legitimate uses of an HTML table, NOT when using it to provide visual layout. When using a table for layout, stick with <table>, <tr>, and <td>, as using the elements below in an unintended manner will hurt more than help.

I was reading an article on making tables accessible, and I wanted to point out some other benefits besides helping screen readers. As you may be aware, in many cases better accessibility means better search engine optimization. Let me point out a few cases where this is true.

Summarizing Content

Using the caption tag and summary attribute gives the search engine something to report, and also a place to put a keyword-rich description of the table that is directly linked to the data, rather than being a nearby unrelated paragraph of text. This simple addition gives meaning to the data in a format understandable by the software that processes your site (Googlebot for example), rather than just the human visitors browsing the search engine results. As for looks, the caption tag can be easily styled as you see fit, just like any other tag, even invisible if you’d like. I’ll leave ethics up to you.

Content Correlation

Roger Johansson mentions using the ’scope’ attibute on your <th> tags. Using <th>’s will help you to begin with, since it differentiates the heading information versus regular content. With the scope attribute defined, it goes even further and informs the search engines what the heading is correlated to. So if you have headings defined in both axes, the search engine can correctly interpret the relationship of the data. Check the example below, with one of each scope highlighted.

The three headings in the first row have a scope of ‘col’ which indicates the data they are referring to is in columns below each of them. Likewise, I set the scope of each person’s name to be ‘row’, which tells the search engine that the data in that row is all related to that name. See how easy it is to spot Bob’s age? This is a pretty simple task for a human even without the help of the scope, but the coloring represents the aid you are supplying to the search engine.

Note that scope can be applied to a <td> just as effectively as a <th>, and when a cell is both data and a heading like the names below, the <td> is the appropriate choice for tagging the headings for each row.

Alternative Search Terms

<th> tags can take an ‘abbr’ attribute. While this is convenient for the screen reader to avoid saying the same three word heading over and over again, it also can come in handy if people end up searching for a less formal but still descriptive term for that column of data. See the ‘Date of Birth’ column in the example source.

Example Table

Employee Birthdays
Name Date of Birth Age
Chris Jun 14, 1983 22
Bob Nov 11, 1979 26
Tom Apr 09, 1976 30

The source (styling excluded):

<table summary="A sample table demonstrating the benefits of the scope attribute within table elements">
  <caption>Employee Birthdays</caption>
  <tr>
    <th scope="col">Name</th>
    <th scope="col" abbr="Birthday">Date of Birth</th>
    <th scope="col">Age</th>
  </tr>
  <tr>
    <td scope="row">Chris</td>
    <td>Jun 14, 1983</td>
    <td>22</td>
  </tr>
  <tr>
    <td scope="row">Bob</td>
    <td>Nov 11, 1979</td>
    <td>26</td>
  </tr>
  <tr>
    <td scope="row">Tom</td>
    <td>Apr 09, 1976</td>
    <td>30</td>
  </tr>
</table>

Category: Web Development, Web Technical

divider
May 1st, 2006
Posted by Chris Ruppel at 7:21 pm

I am a web standards geek. I am a novice, but I definitely try to do it the W3C way if it’s possible. I feel it’s made me a much better developer, having improved both the quality of my work and my understanding of the technologies as a whole. I write pretty clean markup, and go out of my way to separate the various layers of a web page.

Non-standard Standards?

Having said that, it was recently brought to my attention that a common property in JavaScript, innerHTML, is not a W3C property. It is present in IE, Mozilla browsers, KHTML, and Opera, but it is not an actual standard property!! Having ramped up my usage of it recently due to Ajax (which also falls under the umbrella of a ubiquitous non-standard, for now at least), I was pretty let down to learn this. Just about every browser supports it and treats it the exact same way, to the point that it has more univeral support than the actual W3C Recommendation involving ‘createElement’ and ‘createTextNode’. It is clearly a de facto standard, moreso than IE being equated with ‘the internet’ in the minds of many people.

I understand the problems with it , but I feel you have to draw the line at some point. Is it good web design to use innerHTML? Many say no, and some offer an alternative that tries to bridge the innerHTML ease of use with cumbersome W3C methods. As I learn about the varied alternatives I have to ask myself, what is the value of doing something using the ‘technically correct’ method when other alternatives work just as well or better (as in this case)?

Getting the Job Done

When discussing this, a friend of mine said, “good web design is an exponential curve. you never reach perfect.” I find this to be true, and not just to ease my conscience. I realize that this sentiment can be applied on many lower levels (why should I not use spacer gifs?), and my response is nothing is stopping you except your own judgement, just like my choice to continue the use of innerHTML. I’m not trying to nullify other assertions I’ve made in the past, but it is a tough call when you come to such an impasse.

Category: Web Development, Web Technical

divider
right shadow