This October, come to our Bay Area Drupal Camp (BADCamp) booth to give your elected representative a piece of your mind. We won’t be holding members of congress captive at the Kalamuna booth (or will we?) but we’ll have plenty of other excitements there to keep you curious. And of course, BADCamp is a celebration of open-source software, so we’ll be giving plenty of Drupal talks.
Late last year, we upgraded our blog from Drupal 7 to Drupal 8. Our main objective was to invest in our skills within Kalamuna so we could, in turn, better serve our clients. We have a lot of Drupal 8 migrations lined up over the course of the next year or so, and we foresee many more coming down the pipeline. This gave us a chance to learn the ins and outs of Drupal 8, with the added value of sprucing up our very own blog. This post is a summary of takeaways from our experience that I hope will help you on your own Drupal 8 adventures.
Once upon a time, a Drupal shop owner hired a contractor for a project. The contractor signed papers, met the team, and then started work. On the first day, the contractor’s invoice listed “local environment setup” as a line item. On the second day, the contractor’s invoice listed “problems refreshing local environment” as a line item. On the third day, the contractor’s invoice listed “fixing PHP version-related error” as a line item. Are you a character in this story? Does it have a happy ending?
I’m proud to announce that we’re broadening access to Drupal development tools by creating Kalabox 2.0 -- now in the works. The new version, supported by a Kickstarter campaign (and hopefully, you!) will include technologies that will make it faster, easier to use, and accessible to a much wider user base.
Greetings. I'm Kalabot John, and this is my journey with Kettering University and Pantheon Systems.