Problem/Motivation
Portions of the d.o. migration documentation need updating and reorganization. The issues include out-of-date content, poor organization (particularly in the less technical areas), and missing content.
I think the goal here is to provide useful documentation for three primary types of users:
- Those interested in running migrations.
- Those interested in developing migrations.
- Those interested in contributing.
We currently have two main areas of documentation:
- https://www.drupal.org/upgrade/migrate - most of this information is on "Running Migrations", but it needs some work.
- https://www.drupal.org/node/2127611 (Migrate API)
I'm proposing that information for those interested in contributing be located within the "Running Migrations" section, so that we can keep the "Migrate API" section clearly focused on API documentation.
Proposed resolution
I've created a GoogleDoc with the existing outlines in the two main areas (Running Migrations and Migrate API), some brief info about some of the top-ish level pages, as well as some proposed changes to the structure of the "Running Migrations" tree. Feel free to leave comments on the GoogleDoc or below, I'll do my best to compile everything in a way that makes sense.
Remaining tasks
Child issues contain documentation todos. Not all of them are listed here in this issue summary.
Todos from #11.2 which are not covered by child issues:
Additional topics (new)
- Continuous migration (new) - included adding documentation to the issue #2687843: Add back incremental migrations through the UI
- Rollbacks (new) - included adding documentation to the issue #2687849: Add back rollbacks on migrate_drupal_ui
- Using the migrate-manifest drush command (completely rewritten from https://www.drupal.org/node/2350651) - #2914482: Check migrate-manifest documentation on d.o
- Include a sample full manifest file (look in Migrate Drupal tests).
Writing migrations for custom/contributed modules (new) - #2914500: Add documentation for writing custom/contrib modules
- Use core modules as examples, including source plugins, tests, etc… (a bit of a start here: https://www.drupal.org/node/2342695) (new)
- Examples
- When to use templates
- Link to API docs
User interface changes
None.
API changes
None.
Data model changes
None.
Comments
Comment #2
ultimikeReformated GoogleDoc link.
Comment #3
ultimikeFixed typo above.
Comment #4
quietone CreditAttribution: quietone commentedLooks good, just a few questions.
Comment #5
ultimike@quietone,
No - not at all.
There are currently 2 main areas of Migration documentation on Drupal.org:
The documentation for migrate_drupal will be in the Migrate API area.
-mike
Comment #6
quietone CreditAttribution: quietone commentedThx
Comment #7
willwh CreditAttribution: willwh at Drupalize.Me commentedHi Guys,
This landed today: https://www.drupal.org/node/2691023, which removes some fairly significant functionality for running partial migrations.
There are lots of mentions of drush migrate-import --configure-only in the documentation, that are going to require updates.
Comment #11
quietone CreditAttribution: quietone commentedI've gone through the googledoc and compared with the current state of the documentation. I updated the googledoc locally only to find that cutting and pasting my changes into the googledoc totally messes up the formating and makes the document unreadable.
So, in summary nearly all the suggested reorganization has taken place. The two expceptions are
This is a list of the new sections, also listed in the googledoc.
There are issues for adding documentation to the codebase for the migrate plugins. The intention is to have examples of special cases in the handbook.
Next Steps:
Discuss what to do about items 1 and 2 above.
Links:
The Drupal 8 upgrade pages, https://www.drupal.org/docs/8/upgrade
The Drupal 8 Migrate API docs, https://www.drupal.org/docs/8/api/migrate-api
The Drupal 7 upgrade page, https://www.drupal.org/docs/7/upgrade-to-drupal-7
Comment #12
quietone CreditAttribution: quietone commentedComment #13
quietone CreditAttribution: quietone as a volunteer commentedAssigning to myself to update the IS.
Comment #15
quietone CreditAttribution: quietone as a volunteer commentedMade a child issue for item #11.2 , #2914474: Placement of 'top' page explaining upgrade, upgdate and migrate
Comment #16
quietone CreditAttribution: quietone as a volunteer commentedCopied the todo list from #11.2 to the IS and added the sub issues created for each item, so far. Still more to do.
Comment #17
quietone CreditAttribution: quietone as a volunteer commentedFix formatting.
Comment #18
quietone CreditAttribution: quietone as a volunteer commentedSpecifying dependencies (related: https://www.drupal.org/node/2214325). No action needed for this, See #9 in that issue.
Comment #19
quietone CreditAttribution: quietone as a volunteer commentedAdditional topic include an item for 'Others'. None have been added since this issue was created 2 years ago, so ultimike did a great job of identifying what it needed. Marking that with a suggestion to add a new issue if you think of a topic that needs to be added to the docs.
That addresses all the issue in the first section of the Remaining tasks, 'Additional topics (new)'.
Comment #20
quietone CreditAttribution: quietone as a volunteer commentedFix the formatting in the IS again.
Comment #21
quietone CreditAttribution: quietone as a volunteer commentedCreated child issues for the 2 remaining items in the todo list.
Now all the todo items have a child issue or have been fixed. Hopefully, now that this is in smaller chunks we can get this done.
Adding meta to the title.
And thanks to masiplia for offering to help which, in turn, got me to update the issue!
Comment #22
quietone CreditAttribution: quietone as a volunteer commentedUnassigning.
Comment #23
masipila CreditAttribution: masipila as a volunteer commentedCleaned up issue summary.
Comment #24
masipila CreditAttribution: masipila as a volunteer commentedI've now reorganized the Upgrade to Drupal 8 guide and Migrate API guide.
This meta was about reorganizing / adding new pages. I moved the pending 'add new pages' tasks to be children of the meta issue #2561243: [meta] Migration system documentation so that we have only one meta for the missing pages.
Closing this meta as this doesn't have any child issues anymore.
Cheers,
Markus