The past few years have seen a dramatic shift among governments and other public entities toward open data initiatives.
I’ve spent a disproportionate amount of my time over the last year thinking and talking about Personalization in Drupal (just ask my wife), and I’ve had the privilege of working with a brilliant group of people to help design and build a solution for it. Since we launched Lift in February, I’ve also given a large number of demos and discussed Lift in great detail with organizations large and small, learning ever more about what the needs are in the market, and stealing..err..borrowing ideas from them as I go along.
This post marks the first of a multi-part blog series where I hope to distill everything I know about Acquia Lift as a product, as well as personalization, testing and targeting more broadly as we implement these tools.
Cross-posted with permission from Blue Coda With enterprise adoption of Drupal increasing at a rapid rate, many companies are interested in the options available to migrate from legacy systems. For companies using Microsoft’s SharePoint as an external web platform (check out our post about using SharePoint as a CMS), the thought of migrating thousands of pieces of content can seem daunting.
As Drupal continues to gain significant enterprise adoption, it is competing more and more against incumbent technology in the form of commercial and proprietary software.
It all starts with a great idea, something you think will change the world. What’s next?
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.
[Update 09/09/2013] I mentioned below that we'd make our scripts available for setting up BPF.