Commercial Progression is the proud sponsor of the 2015 OSTraining Drupal 8 video training Kickstarter campaign. Among several other topics, one of the sponsored topics for Drupal 8 is search engine optimization. Read on and take advantage of this amazing free resources for the Drupal community.
DrupalCamp Michigan took place on Saturday July 16th, 2016 at the Michigan State University main library in Lansing Michigan. Michigan Drupal developers from across the state arrived bright and early for this day long camp of presentations and panel discussions.
Moving right along demonstrating the new Drupal 8 Object Oriented Programming structure, this next part of my blog series is going to focus on creating a custom field formatter.
I’m taking a break from my Drupal 8 OOP series to help further define something that has not been sufficiently spelled out in all of my D7 -> D8 research: when to use the CMI vs Features.
The configuration management system is meant to facilitate the workflow of development configuration to production, while Features is meant to hold a generic, reusable bundle of functionality.
A recent internal Commercial Progression project allowed us the opportunity to set up a Drupal 8 site and get REST working on it. In the process, and by merit of the stack being new with the documentation catching up, I learned a few tricks that might be useful for enterprising developers out there.
1. POST-ing entities is to a different path than the REST UI says
If you install the REST UI module and enable an endpoint, you'll see a screen like:
In part 2 of my Object Oriented Programming (OOP) for Drupal 8 series, we are going to create an administration form. If you missed part 1, I talked about how to make a simple custom block in D8, which is something we do here at Commercial Progression to brand our sites. I chose a custom block to show that the new changes in D8 aren’t so scary, and to introduce object oriented concepts and definitions with a real-world example.