Dropping IE6 Support

We had a discussion this morning at work about IE6 support started by Blaine Bowers. We have had this conversation several times over the past year but this time we settled on stopping our support for Internet Explorer 6 when Google does, which is March 1st. Microsoft has already dropped support but Google dropping it is a bigger deal as they have some of the most visited sites in the world, including YouTube. This is great news for us at work as we do spend a little time having to fix IE problems. We still plan to support IE6 but at an additional charge if its needed for the client. I am mixed about the choice thought.

On the one hand, IE6 is a pain in the ass sometimes. I know people spend lots of time having to debug and fix problems in this old, outdated, broken, and security mess of a browser. This is time that could be spent doing something more productive then having to support an 8+ year old technology. The web is moving forward and great things are not only on the horizon but most already here. However, dropping support for a browser that, although outdated and a security risk, has a decent market share fully isn’t the best solution. Unless you know the site your doing will not have a noticeable amount of visitors on IE6, then I still believe that the website should be functional in IE6. It won’t look as good as it will in modern browsers like Safari and Firefox or even IE8 but you know what? It doesn’t have to. The site doesn’t need to look exactly the same in every browser. I believe a minimal amount of time should still spent in at least opening a site in IE6 and at least giving it a look over and fixing any major issues that keep the site from being used correctly. I’m even okay with a little message warning users that have IE6 that they should update their browser, but not a warning that covers the website and keeps it from being used.

Although we will not be supporting IE6 by default at Crane|West anymore, I still plan to open each site in IE6 to at the very least give it a look over. The ideal situation of course would be to get a feel for the number of IE6 visitors that the client site will get either based on their current analytics, which sadly aren’t always available, or research on other sites in the field or taking a look at their target audience. Then you can make a decision on whether the time and money spent on providing full support for IE6 is required or needed by the client. When the market share for IE6 drops below 5%, then I believe support around the board should be dropped, but until then, whether we like the browser or not, people do use it. Its just a matter of if those select people are your target audience or not.

QTT: Custom Templates in Kaizen CMS

First a brief intro into Kaizen. Kaizen CMS is still a relatively new (or at least new to the public) content management system that was started by John Hoover back in 2007. The cms that exists today is far from the initial and started to take shape in August of ‘09 and released as open source to the public in January 2010. I’ve worked with John for over a year now (at DigiMedia and now at Crane|West) and joined him in development of this project in October ‘09. It still has areas we are improving on but is the basis we start all of our sites with. The source is hosted on Github and the project is opensource so feel free to fork and explore the code. The project is in active development with lots of improvements in the works.

Now onto the quick tip for today. I’m going to show you how easy it is to create a custom template in Kaizen CMS. Its honestly as easy as one line of code and the cms already has an example of this in ./views/content/contact.tpl file. A custom template is a great way to provide a different look to different pages without affecting the overall site appearance. You might have a page that you don’t want the sidebar to show up on or a page with a completely different header and footer. Kaizen allows you to do this easily without almost no effort on your part. We use smarty for the templates as well. Lets look at the code for the main content template (./views/content.tpl).

1
2
3
4
5
6
7
8
9
10

{include file="inc_header.tpl" page_title=$aContent.name|clean_html menu=$aContent.tag}
 
	<section id="content" class="content">
		<h2>{$aContent.title|clean_html}</h2>
		{$aContent.content|stripslashes}
	</section>
 
	{include file="inc_sidebar.tpl"}
 
{include file="inc_footer.tpl"}

Line 1 does three things. First it includes your header file, in this case it’s inc_header.tpl, then it sets the page title using the content name (page title set in the admin) and last it sets the menu tag (this lets you tell what page your on and can then set a class on your menu to show that. Line 4-5 is displaying the content for the page, so nothing special. Line 8 & 10 are just including the sidebar and footer.
(more…)

Pressing | 1 Minute Short

Typing on a keyboard.

Shot on a Canon Vixia HF200