Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Migrating to Content Moderation with Lightning

196 views

Published on

As underlying modules evolve and change, Acquia Lightning maintains a veneer of functionality on top of them.


A recent major example was the transition from the contributed module Workbench Moderation to the new Core modules Workflows and Content Moderation.

Learn why Acquia Lightning was motivated to make the switch, how it approached the problem, and how you can take advantage of that work ... even if you don't use Lightning.

Presenters:

Adam Balsam - Sr Drupal Dev Tech Lead at Acquia

Adam Hoenich - Software Engineer at Acquia

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Migrating to Content Moderation with Lightning

  1. 1. Migrating to Content Moderation and Workflows
  2. 2. ©2018 Acquia Inc. Who are we? The Lightning Team ● Adam Balsam - balsama on D.O …and other places ● Adam Hoenich - phenaproxima on D.O …and other places - Developer of the WBM2CM module
  3. 3. ©2018 Acquia Inc. What is Lightning A Drupal 8 distribution that bridges the gap between what Drupal does out of the box, and what users want it to do. ● Concentration on API, Layout, Media, and Workflow ● Provides update paths as underlying modules change ● ...and migrations when Core adds overlapping functionality
  4. 4. ©2018 Acquia Inc. What is Workflow? Ability to ● Assign arbitrary states to content entities ● Transition between those states ● React to the state of content
  5. 5. ©2018 Acquia Inc. Original Solution ● Workbench Moderation ○ Not a port of the D7 module ○ But used the name ● Worked so well, that the community decided to rename it and put it in core!
  6. 6. ©2018 Acquia Inc. Content Moderation 8.2.x ● Added as an experimental module (experimental had a different definition back in 8.2.x). ● There were many follow-ups planned and it wasn’t really suitable for production yet. ● Plus, no update paths for experimental modules at the time.
  7. 7. ©2018 Acquia Inc. 8.2.x, 8.3.x, … () ● Lightning continued to use WBM throughout 8.2.x and 8.3.x ● Content Moderation underwent significant changes during this time including: ○ Abstraction of states & transitions into their own module: Workflows ○ Replaced the field widget
  8. 8. ©2018 Acquia Inc. 8.4.x New Core policy: Experimental modules will have at least beta stability and will provide update paths Decided Lightning would migrate given the following: ○ Lightning functional tests must pass with CM ○ Content moderation feature complete when compared to WBM ○ A stable migration path
  9. 9. ©2018 Acquia Inc. Functional Tests ● Relatively low-hanging ● Required a new solution for scheduling
  10. 10. ©2018 Acquia Inc. Feature Complete ● Quick edit awareness ● View integration ● Multiple forward translations
  11. 11. ©2018 Acquia Inc. Migration Path! ● Released as a separate module https://www.drupal.org/project/wbm2cm ● Uses core Migrate module
  12. 12. ©2018 Acquia Inc. Data 1. Store states and remove them from entities 2. Uninstall WBM, Install CM/Workflow 3. Map the stored states back
  13. 13. ©2018 Acquia Inc. Workflows Groups states/transitions instead of assigning per bundle
  14. 14. ©2018 Acquia Inc. Questions for Adam H 1. Did you have any help with the WBM2CM module? 2. Why Migrate instead of, e.g. Batch? 3. Can you describe in detail what steps Migrate takes? 4. How does a user trigger the migration? 5. What can a user expect while running the migration? 6. What are the generated Workflows named? 7. Any caveats?
  15. 15. Questions from attendees?

×