This is my first Drupal 7 eCommerce site. I considered Drupal Commerce but ultimately chose Ubercart due to 1) familiarity (this was my 6th UC site) and 2) I *loathe* DC's two-nodes-per-product paradigm (good for us, bad for clients).

The design is responsive and I gave Adaptive Themes a shot for the theme (for the first and last time). Moving forward, I won't be using any base themes as they (or at least AT) adds a lot of unnecessary overhead.

I'm happy to talk about modules and whatnot - check it out: www.eye-hole.com

Comments

end user’s picture

Looks good and clean design although in Firefox 12/Linux Mint 11 the upper menu is causing a horizontal scroll bar on my screen.

Bricks and Clicks Marketing’s picture

Can you show me screenshot?

Arp Laszlo
bricksandclicks.marketing
design / theming / development / consulting

end user’s picture

http://www.getubercart.com/images/do/eye-hole.jpg

If you don't have access to a Linux install I'd download Virtual Box and install Linux Mint or one of the smaller distros. You can run it at the same time as Windows and check your sites as you work one them. I do the reverse with windows.

bojanz’s picture

Note that Commerce now has a solution for those finding the product->product_display node separation problematic: http://drupal.org/project/inline_entity_form
The linked module makes it behave Ubercart-ish while still keeping architectural purity.

Bricks and Clicks Marketing’s picture

I tried DC first (wanting to try the presumably newer/improved) & didn't come across this module while trying to automate creation of product displays. I'm not getting the 'architectural purity' of DC's approach, it just doesn't make sense to me. How is it beneficial to a client?

Arp Laszlo
bricksandclicks.marketing
design / theming / development / consulting

bojanz’s picture

I am not planning to start a Commerce VS Ubercart flamewar here. I'm glad your project has been successful.

That said, clients don't really benefit from sound architecture, at least not at first. Developers do, and that is something that the client feels as well, sooner or later.
I personally believe that it is vital for each variation to be a separate entity, however you call it. Code-wise it is much less painful.
That doesn't mean the client needs to ever know, hence my module (Inline Entity Form).

My goal was to provide some info, which I've accomplished, carry on :)

cpk’s picture

I was going to complement you on your checkout pages, but it looks like you've switched to SquareSpace for a checkout process instead of using Übercart for checkout. So, I guess what I really like is the SquareSpace solution.