My apologies for those skipping through the travelogue to get to the Drupal... Or skipping through the Drupal to get to the travelogue. If I do my usual (painfully) painstaking editing job my DrupalCon posts will come out in July, so I'm settling for a chronological stream-of-consciousness here for the sake of timeliness.
To expand on the “Going forward” section of my last blog post, there’s still a lot of work to be done to get the migration ecosystem for Drupal 8 up to the level it was for Drupal 7 - as well as taking it beyond, as I believe the D8 architecture enables far more powerful and flexible tools. As an independent consultant, I have a more flexible schedule and more time for pure community work, but with great flexibility comes great… dithering.
Migrations are now plugins
Business modelsGenerally, in the past I've been involved in migration projects from end-to-end:
- Analyzing source data, and working with site-builders and stakeholders to work out what legacy data maps to what Drupal entities.
- Architecting the migration implementation - figuring out an optimal class hierarchy, constructing the initial implementation, etc.
|Basic migration framework||migrate (contrib)||migrate (core), plus destination plugins in core modules||Experimental|
|General-purpose drush commands||migrate (contrib)||migrate_tools (contrib)||The most common commands (ms, mi, mr, etc.) are working|