Drupal 8 has been out for 2 months now, and there's never been a better time to choose Drupal for your website platform. Here are 8 reasons why!
1. Mobile Experience
Drupal 8 is mobile first. Every bit of Drupal 8 can be easily managed from your smartphone, with a responsive experience that works well right up to the widest displays.
You don't need a separate mobile site.
We're digging into our first dry-run migrations from Drupal 6 to Drupal 8, and learning a lot about what's ready and what's not. And there's some surprises in there...
I'm sure many of you reading this may have heard that Drupal 8 has been released, may have even received some marketing emails.
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.
Freelock has a deep bench in all things Drupal, but beyond the technical skills they also offer the much-appreciated ability to ask the right questions, articulate issues, and offer strong solutions. They were a true partner that went the extra mile amidst shifting priorities and deadlines. I look forward to a continued working relationship with the team at Freelock.UW Center for Reinventing Public Education