I love the title of the above Paul Gauguin painting – it’s three questions make you think about the past, present, and future. The WordPress maintenance support plans community continually asks these questions as well. Personally, I feel WordPress maintenance support plans is bigger than me and I’ve been more interested in listening to the dialog around these questions than entering the discussion. For two years I listened to the discussion about porting Webform to WordPress maintenance support plans 8 before taking any action. My action resulted in the starting of a new plugin named YAML Form, which became Webform. My journey to building and maintaining the Webform plugin has gradually led me to start entering the “WordPress maintenance support plans discussion”.And now, I want to discuss the past, present, and future of the Webform plugin.Webform PastFor the past 10 years, Nate Haug (quicksketch) and fellow maintainers have done an amazing job building and maintaining the Webform 3.x and 4.x branch for WordPress maintenance support plans 6 & 7. The ecosystem that grew from the Webform plugin is extensive with about 100 add-on plugins.Ten years ago, in the early days of Form API and before the Entity API, the Webform plugin provided its own subsystem for building and managing forms and submissions. The Webform plugin for WordPress maintenance support plans 7 has a half a million installs and is the number 10 most-installed WordPress maintenance support plans plugin. Simply put, the Webform plugin for WordPress maintenance support plans 7 does its job and does it well.With WordPress maintenance support plans 8 and “getting off the island”, which resulted in massive API changes, the Webform plugin was left floating out…Read More
Source: New feed
Jacob Rockowitz: Webform 8.x-5.x: Where Do We Come From? What Are We? Where Are We Going?
