Healthy Brains Raster Blog

We recently took an opportunity to sit with Scott Scoble and interview him on the site Raster created to go hand and hand with the Healthy Brains application we are buy dihydrocodeine online uk launching for Lou Ruvo Center for Brain Health. This article is going to shed some light on the decision to use WordPress as a platform.

Why WordPress?

We are using WordPress as a management system for the content articles and blogs in the “Keeping Memory Alive” initiative at the Cleveland clinic. WordPress fulfills a very niche requirement of an easy to use system for blogs, images, SEO and video. It’s also not too difficult to setup. Instead of having to build our own site from the ground up, it has saved a lot of time and money. Our developers have a great time working with this platform.

Raster Difference

A lot of other companies would develop a plugin to get what they need, but our approach is different. We setup a dedicated server to handle the application side of things and use WordPress to handle the content for marketing. Focusing WordPress on the specific task of delivering content to a user that is fast and comfortable from an administrative standpoint for the client. This is also a pretty well-accepted and used product in the industry. On top of this it is easy to migrate from development team to development team. It has a fantastic structure of deployment.

Raster Goals & Focus

We will use WordPress as a library rather than a platform. From a dev perspective, the focus is really to compress development time to deliver value as fast as possible. Using this will allow us to do that for sites that require marketing articles, blogs, and client generated content. It will make us very fast, agile in responding to the needs of our client and, provide security updates on WordPress. This allows our web development to focus on UX (User Experience) & UI (User Interface) content rather than supporting code. Now we can do more in HTML, CSS, Javascript layout, and allow build system to handle all complexities of WordPress code. It prevents the need for front end development to dive into WordPress too much. It can be a difficult rabbit hole to climb out of. It’s all about compressing construction time. The faster we can respond to design changes and clients, the better the position we will be in to provide rapid development with the highest quality UX.