I am proud to announce that the latest version of Agnostic Dev has been redeveloped and is now up and running on top of Drupal 8. I am very happy that the entire development process went very smoothly and from start to finish only took me about two weeks. This is a significant improvement over what it took to develop the Drupal 7 version of Agnostic Dev as it took me close to a month and I did not have any content to port. Along with the smooth development process there were also many valuable lessons that I picked up about Drupal 8 along the way.
Lately I have been working with Drupal 8 trying to get my head around what it takes to create a production application in the latest version of Drupal. One of the very first snags I hit was theming. Working with the theme system in Drupal 8 is quite a bit different from Drupal 7 beings how Drupal 8 utilizes Twig as the theme engine instead of PHPTemplate. Drupal 8 was my first exposure to Twig so diving right into development came with a bit of a learning curve to get started.
Over the last year or so the Drupal projects I have been involved with at work have required the need to work with a lot of video files being maintained in Drupal. Well, as you can imagine the larger the files we are maintaining the greater the strain this puts on our host to serve the files. To try and account for this we moved as many of the assets in Drupal as we could off to a Rackspace Cloud Files account so they could be served from a cloud delivery network.
Over the last couple of months I have been struggling with an idea that involved using Drupal as the content management system and the web service for an application that I am currently building in iOS and Android. The reason I am struggling with this idea is because I am using Drupal 7 and Drupal 7 was not intended to serve data to a web service, but rather to serve web pages.
Over the last couple of years in building Drupal sites I have seen a trend start to emerge in the way content is created. Customers are starting to request more and more content types that are built to support embedded video. That is pretty straigh forward from a development standpoint, right, build a content type that has a textarea that out puts the iframe right on the page or build build a textfield that a user can add a URL and then in your node template pick up that data and output it in an iFrame. Sort of a straight forward idea, right?
Drupal 8, from a brief look, did not look like it had changed much from Drupal 7, but once I really started comparing the features available now in Drupal 8 core to old features that came packaged with Drupal 7 core, I really started getting excited about what is in store for us in the next version of Drupal. To get the full scope of all the new features that come packaged with Drupal 8, I updated my local XAMPP server and went through the complete installation process.