I love the title of the above Paul Gauguin painting – it’s three questions make you think about the past, present, and future. The Drupal maintenance support plans community continually asks these questions as well. Personally, I feel Drupal 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 Drupal maintenance support plans 8 before taking any action. My action resulted in the starting of a new module named YAML Form, which became Webform. My journey to building and maintaining the Webform module has gradually led me to start entering the “Drupal maintenance support plans discussion”.And now, I want to discuss the past, present, and future of the Webform module.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 Drupal maintenance support plans 6 & 7. The ecosystem that grew from the Webform module is extensive with about 100 add-on modules.Ten years ago, in the early days of Form API and before the Entity API, the Webform module provided its own subsystem for building and managing forms and submissions. The Webform module for Drupal maintenance support plans 7 has a half a million installs and is the number 10 most-installed Drupal maintenance support plans module. Simply put, the Webform module for Drupal maintenance support plans 7 does its job and does it well.With Drupal maintenance support plans 8 and “getting off the island”, which resulted in massive API changes, the Webform module was left floating out…Read More
Source: New feed