My name is Tim Smith and I just launched my blog as well. Any feeling of excitement and anxiety that you may have, I totally can relate with. I subcribed and I hope that this blog is successful.

Thanks for the comments! I think it used to be mostly pragmatism that compelled developers to continue to support IE6, but realistically we can’t justify spending our time on it, and in the last several months the push has REALLY been felt online and across social media. I think the nails are firmly planted in the coffin, so to speak. Thanks for reading, and PS you do great work, I checked out your portfolio

I already gave up supporting IE6 in my online apps, instead of that just made a notice on top when you open in IE6 that half of the functionality sad fully is disabled… I really do not think it is worth keeping giving support. Of course I understand some people will debate this but in general… IE6 is dead… long live IE8 (and firefox, and safari and also definitely chrome)

Thanks. Interesting that no one is arguing in defense of WordPress on this one. Perhaps there is less loyalty than I originally thought?

You are absolutely correct about “following what you’re told”. Perception is reality, and people are readily led down one path with the common methods – heavy marketing, endorsements and such. The truth is none of that has to do with actual delivery of promises, there are only suggestions of the product’s quality.

I think the popularity of WP and Joombo is a classic case of following what you’re told. While it’s easier to listen to the masses and use what they recommend, I’m glad I conducted my own research which led me to TYPOlight a few years back.

I have a good buddy who always preaches the benefits of Plone and Zope … I call it “Plope” just to razz him.

The fact is that these things can co-exist, far beyond using WP for content and osCommerce for ecommerce … or throwing an instance of TinyMCE into the mix of some random shopping cart.

It can happen … and it does happen. It just requires an organization who cares more than to hear the first guy who raises his hand and says “Here is a good way to make it look cool without spending too much money.”

Companies are cheap these days, and very short-sighted. When they look at a huge return like the old days of a Dot Com Lamborghini and a huge ROI in the first quarter, they kill the chance of doing something right, sustainable, and future-oriented.

Now, a system that handles idiots in the boardrooms, geeks who want to take pride in their work, and CFOs who can “get it” enough to produce the budget for it … then we have something.

That is my rant. Cheers!

It’s sounds very promising! Today i saw on Twitter that Beta will available in September. Great! I’m waiting for this.
Best regards and keep your good work guys!

Thank you for reading and commenting! Your English is excellent, it is better than my Polish, trust me on that!

The system does share some code with the Catalog module, but only in one backend tool. It does not need Catalog to run though – it is completely stand alone. It has several backend and frontend modules to it, for example

- shipping and payment module management on the backend
- email template and configuration management tool (contributed by Andreas Schempp (www.iserv.ch)
- store configuration tool for general store settings
- isotope file manager for product images and other media
- tax management module
- order management module

Frontend modules include

- shopping cart (mini and full)
- product lister (more on that later)
- product reader
- product options, completely configurable by site admins
- checkout
- customer address book mgmt

The license is LGPL for these. We’ve spent a lot of time making it designer and developer-friendly, and we’ve spent a lot of time making sure this integrates seamlessly with TYPOlight itself. Product categories are actually pages, the reason we did that is because we could then have categories integrated as part of navigation, as well as letting categories enjoy all the benefits that regular TYPOlight pages enjoy such as protection, etc.

In addition, we’ve done a lot of work with the GD library and image scaling is done when needed.

There is more to come as well. We have scratch built everything but the catalog code we started with (Andreas Schempp and I, and the project has been primarily sponsored by where I work, Winans Creative).

Other modules in progress are second-tier items such as pricing rules, we have a gift registry module that is a derivative of the base shopping cart model, and we also have payment gateways for Authorize.net, Postfinance (swiss payment tool), and Paypal.

There is much more in terms of features that I can’t cover here, especially when it comes to media management and our general integrative approach. If you know how to use TYPOlight, there is nothing new with Isotope E-commerce to learn.

So, we are VERY excited about this, it is a paradigm shift for e-commerce and will present more flexibility that we can forsee at this time by virtue of its design. The skills needed to use it are no more than what you already have. Although you can go deeper into it, the most common items are right at your fingertips, so to speak.

I’m big fan of TYPOlight and nice to hear that will new e-commerce system for this CMS. Can you describe little bit more about this? Is it based on any existing module like Catalog? (German e-commerce solution for TYPOlight is based on Catalog that’s why I’m asking). Or is it modul (modules?) writing from scratch by you? I’m really looking forward for this. What about licence?

Sorry for my english.