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.
We're starting to recommend Drupal 8 for some new upgrade projects, with the following notes...
... this statement applies to just about any endeavor you can imagine... I've mostly heard it associated with education, the idea that you can get a good education anywhere if you work diligently at it and learn what the teacher has to teach -- and likewise, you can often skate by in good schools without coming out the other end with much learned.
Mike, looking for information about integrating a data collection Software as a Service (SaaS) offering, asked:
I was a little surprised by your comment that the capabilities aren’t likely to be available in an existing widget. I was under the (I guess incorrect) that Drupal was more sophisticated and locked down than WordPress, but that similar widgets could be found – even if the choice is more limited. I’ve found WordPress widgets that offer some of the features, and that could be adapted.
Lately at Freelock, we've been improving our Drupal site assessment. For years we've analyzed Drupal sites built by others to identify how well they are built, what pitfalls/minefields lurk there, and where we need to be extremely careful with budget recommendations when extending functionality.
In the past couple months, we've overhauled it to include a snapshot rating of the site, to let our clients know what we think of their site in 7 crucial areas.
One of them that's often overlooked is Maintainability.
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