Today marks the release of Drupal 8, and the birthday of its founder, Dries Buytaert. This release is more than just a new digit, it's an entirely new platform with something for everyone to love, but it's particularly big for web site owners.
What's the big deal? The biggest, most powerful, one of the most successful open source projects in the world has two major, fundamental changes that change everything you thought you knew about it.
Well, not everything. Lots of the things that people love about Drupal are getting some nice improvements:
Here are the slides from my 2015 Drupal Summit talk, Quality Drupal DevOps!
Drupal 8 has only 4 critical issues before getting released out of beta! Fingers crossed for a release this week!
The major issues that remain are:
Faster, more secure, more maintainable. Three nice benefits we get from our new standard Drupal server architecture.
This year we're replacing our old "traditional" LAMP stack with an entirely less pronounceable LNDMPS version. We still use Linux, MariaDB and PHP, of course, but instead of Apache we've moved to Nginx, and we've added Docker and Salt.
We hear it all the time:
Why do you recommend a 6 hour budget for a simple integration? Here's an embed widget right here -- if this were WordPress I could do it myself!
More and more I keep running into assertions that Git is a version control tool, and that if you use it for deployment, you're doing it wrong.
At Freelock we find it to be a very effective deployment tool, and I'm not seeing a solution that meets our needs any better.
Two presentations in particular caught my attention recently mentioned this:
For many years, we've organized our development around user stories. What exactly is each user trying to accomplish, and what does that look like when they try to accomplish those tasks?
For most of the past year, we've taken this a step further and adopted Behavior Driven Design. It's the same thing, really, with one fundamental difference: we have a tool to automate testing the user stories, and a more specific syntax to use that gets straight to the heart of the user story.
Another sales call today, with a prospective start-upper who thought Drupal might lower his costs to get a web startup launched.
And I didn't really answer the question directly -- because in the long run, if you're building something successful, you're going to spend as much on your Drupal site as you would building from scratch.
The key difference? How quickly you can get something in front of users that might help you get some traction and build your business.
We recently had a new client contact us and ask if we could move their sites over to Pantheon so they could do some in-house development work. Of course we can do that for you! We recommended doing a Site Assessment for them, just to make sure we know what we're dealing with. Our Site Assessment gives us a good understanding of the state of a client's current site.
What a pleasure to work with Freelock in launching our family website for the West Seattle community. John and Jill were vital to our success. We quickly saw that Drupal could handle our scope of requirements and thrilled to find that many of our wish list features were doable with such a capable staff. Communication and support are out of this world impressive with the Freelock team and set the standard for the industry. On time and in budget. Freelock is the clear choice.West Seattle Family Zone