Home / Resources / Blog

Featured post: A Reflection on Karen McGranes DrupalCon Portland Keynote

Katelyn Fogarty's picture

I just finished listening to the DrupalCon Portland’s Wednesday keynote presented by Karen McGrane about UX experience and content for all devices.

[I'll add the keynote video once it is posted, but I didn't want to wait to share my thoughts]

What I took away from her talk was, we need to start thinking about our content in a way that can be used in many places and not just thinking about the one spot we want it in at this very moment we request it. Wow is this really a new way of thinking? I’ve been working with Drupal for the past 5 years starting with Drupal 5 in 2008. At my last job prior to Acquia the team I worked on built all our sites on Drupal 6 exactly how Karen was recommending, but the end users weren’t ready for that approach. We built a content type that would create just a page full of meta data related to each one of our products. Some example fields we used were; image fields to upload the product box image at every angle, 150 character product overview field, 300 character product overview field, feature list field, benefits field and so on. This node was then used to populate views and template files that created our product pages, store pages and paid search landing pages throughout our website. Those fields were then able to be edited in one place and changed everywhere. We didn’t build the site responsive at that time but we would have easily had all the content available to use however we wanted if we did.

More...

Our blog

Business

The Truth About WYWISYG Editing in your CMS

Tom Wentworth's picture
Yesterday at DrupalCon I saw Karen McGrane speak for the first time. Karen is a respected content strategist and frequent keynote speaker. She's fantastic, and I was thrilled to see her speak live for the first time. The main point made during Karen’s keynote is that we need to think differently when thinking about digital content. Legacy processes designed for print publishing shaped much of... More

Technology

Automate review for security risks with source code analysis

Ben Jeavons's picture
Security issues are created in custom code when developers cut corners during development or don't make proper use of the APIs, among other reasons. There are several ways to discover such issues, including peer-review, code scanners, vulnerability scanning, and even by being exploited -- tho certainly undesirable! While each has its place and individual merits, let’s talk about security-focused... More

Design

Notes from Views Mini-Course, Part II: Creating Flexible Views with Drupal

Heather James's picture
Here are notes from the 2nd class in our Views mini-course. Watch the recording Views Mini-Course, Part II: Creating Flexible Views with Drupal 7. Review the notes and recording from last week. Sign up to Views Mini-Course, Part III: How to back up your Views safely. May 15th. In today's class we will look at the Views UI in detail. I'll show you how to create flexible views.... More

Latest posts

Lullabot podcast #65

Default avatar
I was featured on the infamous Lullabot podcast series. Jeff Robbins and I talk about Acquia, Mollom and Drupal 7. Check out the Lullabot podcast #65 (mirror) if you want. We kick it off talking about Acquia, the Mollom part starts around minute 25 and the Drupal... More

Setting up Acquia Drupal on GoDaddy Hosting

Joshua Brauer's picture
This set of screenshots grew out of a recent forum post on the Acquia Network forums. It walks through setting up a GoDaddy Linux hosting account to use Acquia Drupal. At the end of the process one has a new website. Some will scoff at the choice of GoDaddy as a hosting platform. Many shared hosts have shortcomings in different areas. Few shared hosts are going to be getting glowing recommendations on the day your site ends up on the front page of Digg, they simply aren't built for that sort of load. However,... More

Introducing the Acquia Partner Program

Chuck D'Antonio's picture
Today we launch the Acquia Partner program with [fourteen partners](/partners/finder) ranging from [sole proprietorships](/partners/showcase/33rd-prime) to [venture-backed firms](/partners/showcase/optaros). I'm excited by the diversity of partners in the program; partnering with different sizes and types of firms will help our customers find the match that maximizes their success. We've been able to enlist parters from [Israel](/partners/showcase/linnovate), the [UK](/partners/showcase/io1-limited), the [US](/partners/showcase/pingvision), and [Canada](/partners/showcase/raincity-studios... More

The way the web should work

Linea Rowe's picture
In the Spring of 2007, I teamed up with Partners in Health, a non-profit building hospitals in developing countries. We had a long list of ideas for an intranet and for a new public site and needed a tool with a lot of flexibility. We picked Drupal because of the active community, the growing collection of modules, and the hope that non-engineers could administer the sites. The Partners in Health sites went up fast. In a matter of weeks, people from around the world were downloading and using materials from the sites to help train health workers in rural parts of Africa and Latin America. As... More

Keeping Acquia Drupal in Sync

Default avatar
We did a security release of Acquia Drupal yesterday in order to incorporate the security fixes in the core Drupal 6.5 release. One of the internal goals of the Acquia engineering team is to respond to security releases of Drupal core, or any of the contributed modules in our distribution, by updating our Acquia Drupal release within 24 hours. We want to ensure that Acquia Drupal sites stay in sync with the most secure code from the Drupal community. Drupal 6.5 was the the first test of our engineering release process since Acquia Drupal came out of beta. While we... More

Pages