I am proud to say that I wrote the whole TASCAM website, and can claim credit for about 75% of the design as well.
Here are some words I have to say about about the site, and my experiences working on it.

Things that are true about this project

• This is a project that I manage on an on-going basis, periodically making changes to the site's architecture and adding new features.
• I played a large role in creating the site's design; from mockup conceptualization and creation(60% mine), to several generations revisions and approval(80% mine), and finally, execution and production(100% mine).
• Features a custom object oriented Content Management / Site Administration System with secure login and multi-user, multi-level permission system.
• Data Migration: From two completely different sources; A previously existing JP website, and a previously existing EN website.
• There is more Japanese content than there is English content.
• The site's engine and architecture was designed with multi-regionality and future upgrades in mind; There are plans to migrate/add European, Canadian, Mexican, Korean and Chinese localizations to the current server using this structure once company internal politics have been resolved.
• You have no idea how sick and twisted the architecture for the database for the previous EN site was. You needed to query no fewer than 16 tables to get all the data you needed for any one page. That was a nightmare.
• This particular design required the production of over 9000 graphic assets; 2 special graphics for each product, and 1 localized product image per region to cross-link between products.
• Internet Exploder made everything a pain, again. Thankfully, I'm getting ever more awesome at writing code that even Exploder can't hiccup on.
• I can't read or write a lick of Japanese. We hired out the initial content population on the JP half of the site to an anime nerd friend of mine.
• I wrote the whole site by hand, from scratch, with my favorite text editor, BBEdit.
• The functional (non-content) parts of the site's code are less than 768 KB total.
• Lightweight, high performance, low latency site architecture with a low memory profile; Runs in a virtualized multi-hosting environment and takes less than 256 MB ram total for all server instances.
• My CMS/Administration tool set needed an upgrade, so I took all the notes I had taken and all of the lesons I learned from all previous projects and implemented all of my best practices into a new tool set that would be versatile and reusable. The result was Darth Validator 4, and my new Lister class. This makes building new most new content management tools extremely quick and easy.
• If you look in my CSS, you'll find a few selectors with a Z-Index of over 9000.
• In one of the mockups displayed below, there is mention of a "Solid Snake" recorder.
• I still think the site would have looked better in black and blue like my first mockup.
• There used to be a Cheezburger on the homepage. Every site I design looks good with a Cheezburger on the homepage.
• I think there were even some dinosaurs on the homepage at one time.
• Happycat makes no appearances on this site at all, because he has no interest in pro-audio hardware.
• Jeff probably owes me a drink. Maybe ten.
• There were a few nights that I worked on the site for no fewer than 36 hours in a row to meet feature enhancement deadlines.
• I had to buy "Apology flowers" for my girlfriend no fewer than 8 times because of this project.

Things that are NOT true about this project

• Microsoft software was successfully used to create meaningful output that did not need to be re-created from scratch using other software because of how good the initial output was.
• Microsoft server products are being utilized for this site's hosting.
• Working in a different language and/or time-zone than your client always makes communication very, very easy.
• Oniki-san probably does not owe me 20 drinks.
• It was a really good idea to organize the site by the concept that a product can exist in multiple categories, and can exist within multiple applications, and this hierarchy should be region dependent. This structure makes sense to visitors of the site, and customers want to see a different list of product categories depending on which application has been selected.

Screenshots of the current live site

Mockups, Conceptualization & Pre-production

You know, the parts you have to do to figure out what the client likes, and then when you're designing the workflow that you'll be using to produce all of the graphic and data assets that you'll be populating the site with before launching.

This was one preview of how the architecture of the site can handle displaying slightly different layouts per region, and display more or less data on a page depending on the attention span of a particular region's audience.

Two slightly different versions of the product page that were later re-designed

Also, I am convinced that the sites that I design look way cooler with japanese dummy content than with english dummy content.