Macromedia.com “Day 1″ Web Site

The "Day 1" macromedia.com web site has arrived! The "Day 1" site is how we've been referring to the modified macromedia.com web site that would go live once Macromedia became "the company formerly know as…".
Which is now! As the chief info architect for the web site I wanted to have
the chance to explain some of the things we did and why.

 

Design goals for Day 1 Web Site

(1) Ease transition pains for users
We knew we had to make some changes
to macromedia.com to communicate to folks that we are now Adobe. But we were
concerned that making any drastic changes to the web site would hurt our regular
visitors and customers (or at least inconvenience them, which is the same thing).
Ever since one fateful redesign many years ago, we've been chanting "evolution,
not revolution" every
time a redesign comes due. So our number one design goal for the Day 1 macromedia.com
web site was "do no harm". We wanted to allow developers and others who use
the site on a regular basis to easily get to information and resources they
use regularly (dev center, support, forums, downloads, Labs, etc).

(2) Answer the important question: what about me?
We also anticipated
that folks would have concerns and questions about their products ("are you
still going to support <ProductName>?") and their relationship with
us. So we wanted to provide easy site-wide access to acquisition information
that would help answer these questions.

(3) Allow easy cross-travel
We know that many
of our customers use both Macromedia and Adobe products And
that many are regular users of both sites. For the "Day 1" web site we wanted
to create a convention for crosslinking that would allow easy access to and
from each company's
web site in places where it made sense. Some examples are the home pages for
support, products, downloads, and solutions.

(4) Provide contextual help
The
convention we used for crosslinking not only gets the user to the parallel
area on the other web site, it also provides contextual help where relevant.
For example on the support home the crosslinking pod contains: "Have questions about how this affects your support? Learn more