Creating a New Website: A perfect balance of usability, information and culture

In my second post about ReadyTalk’s new website, I’m going to look at how the redesign will affect our customers, and what we’re doing to improve the ReadyTalk experience, and what you can expect from our website blog posts. If you haven’t heard, we’ll be working hard in the coming months to move to a new website that should offer some great features to our visitors and make life easier for our marketing team.

Why are we making the move? In my previous post, I explored our reasoning for moving the site to a content management system called Drupal, and how that will make content creation and management a fast and simple process for ReadyTalk. That’s just one of the reasons for our redesign. We’ve also been conducting a lot of user testing to make sure that our site direction meets the needs of customers. For instance, our navigation will be changing to make finding important information easier for our customers and prospects. Our new design has also been tailored to ensure that any changes are comfortable for our current users. As always, logging in to ReadyTalk will be a one-step process, and it will still be the first thing you see on the front page.

In addition to the practical side of a redesign, we also recognize the opportunity to have a little fun, too. Expect to see our culture represented in new and different ways on the website. We love what we do, and we want to make sure the world knows it! If you need any proof, just see JC’s post about our engineering department.

In the coming weeks, you can expect to hear a lot about the website. We’ll be exploring our processes and discoveries along the way. Here are some topics you can expect from ReadyTalk:

  • Usability testing
  • Design and mockup processes
  • Improving SEO with Drupal
  • Integrating a jQuery carousel in to Drupal
  • The power of Drupal and views

 

Are there other topics of our redesign that you would like to see us cover? Do you have questions about how we are implementing Drupal? If you have best practices or some favorite resources, please share in the comments.

Share this: