This is my blog.There are many like it, but this one is mine.
This weekend I enjoyed WordCamp New York City as well as a gorgeous 6-hour drive through the Adirondacks to get there. While the presentations on deploying WordPress in a Hybrid, Serverless or Headless approach were what caught my attention going to New York, it was Andrew Roberts session on the What and Why of Gutenberg which piqued most of my thoughts and subsequent conversations during the weekend. This post looks at common areas / approaches to working with WordPress in a post-Gutenberg world based on info I learned during the #wcnyc weekend.
Apply Filters recently put out a call for development-centric questions. I offered up a question in a haphazard series of tweets relating to different approaches to extending / customizing the WordPress Rest API. This article expands on that question and looks at 3 different approaches to customize / extend the Rest API infrastructure built into WordPress as of 4.7.
I hardly felt that ~20 lines of code is worth an entire blog post. So why are you able to read this as more than a tweet? The more I looked back at the potential approaches to solve this problem I could have taken, the more I realized understanding how to figure out the minimum viable code to complete a requirement was worth exploring. Especially when this snippet could be used in a LOT of common business processes.
There are multiple ways to generate bulk Gravity Forms entries which trigger Gravity Flow workflows. You may benefit from using a bash script looping Gravity Flow CLI commands OR a function hooked to gform_pre_submission that enables Gravity Forms Entry Importer from Gravity View to map hidden email fields into Gravity Flow user / assignee fields.