Drupal

After many weeks and months of meetings, the decision has been made to finally replace your old website with a shiny new one. Out with the old static site from several years ago and in with a new robust, modern web application which will form the hub for your online presence. You have done your due diligence and your platform of choice is Drupal (good choice we say!).

While writing this article, another critical Drupal core security update was released. Thinkbean clients: Rest assured, (just as with Drupalgeddon 1.0, 2.0, etc.) your site was protected from this exploit... even before the public announcement! EVERYONE ELSE: READ THIS NOW!

Excellent user experience (UX) is a major part of what makes an online business interaction a customer service win. A multitude of companies and services are at the fingertips of anyone who owns a computer or smartphone - 24 hours a day. If a visitor has to spend a long time trying to utilize the information or services on a website... well, they just won’t. They will move on to a competitor whose website meets their needs.

Boston Web Development Team Chooses Drupal for the Future

More than 7 million people come to Boston.gov annually to access city services but the old technology and clunky design wasn’t helping the public or the city employees save time. It was time for a redesign. Boston public servants wanted to deliver a site to the public that was adaptable, user-friendly, and would evolve with the needs of it’s constituents.

Should You Standardize on a Single CMS?

There’s too little conversation about standardization regarding content management systems (CMS), and too much business value lost in not considering it. We’ve written an eBook discussing the topic, but how do you know if standardizing is right for you?

The key to success with any web project – from app design to a new site build to adding interactive functionality – starts with intention. To create a more purposeful web, it’s important to challenge clients who know what they want but not what they need.

With any project – big or small, rescue or new – we start our process with a Discovery.

The Discovery process is simple – it’s an open, straightforward conversation that uncovers two important pieces of information:

No one wants to be the person who invested hundreds of thousands of their company’s dollars into a new website, application or digital asset and then have it fail to meet its expectations.

Even fewer people want to be the ones to then tell their management team the project needs even more investment – sometimes, as much as the initial expenditure – to fix the problems; or worse, start over.

Subscribe to Drupal