[META] Add more information than just module update status

jenlampton commented 3 years ago

I have a spreadsheet that I prepare when I'm working on Drupal to Backdrop upgrades, and it includes a tab for contrib modules, but also has a bunch of other information. I'd love to automate the collection and display of this information from existing Drupal 7 sites, and it seems that there's no better place for it than within this module. I haven't yet decided where it should go (perhaps on sub-tabs? Perhaps a separate report page?) but here's a list of what I'd like to include:

[x] Modules (Drupal core)
[x] Modules (Drupal contrib)
[x] Modules (custom)
[x] Content overview (node types, and counts of each type)
[x] Taxonomy overview (term types, and counts of each type)
[x] User overview (account statuses, and counts of each type)
[x] Paragraph overview (paragraph types, and counts of each type)
[x] Field overview (and field types that might be complicated to upgrade into B)
[x] Views overview (and views that are in code instead of in the DB)
[x] Features overview (and content types that need to be updated)

I'm not yet sure how to tackle these, since it will involve some "evaluation" of the custom code, but maybe for now we can simply list that these exist, and expand information about them at a later point in time?

Custom module(s) and approx complexity of each
Custom theme(s) and approx complexity of each

And here are some nice-to-haves

Panels => Layouts conversions (if Panels was used in D7) and possible mappings
Contexts (if Contexts was used in D7)

jenlampton commented 3 years ago

I've started a PR with a reports page and so far it has content types, vocabularies, and users.

jenlampton commented 3 years ago

I've pushed some commits that added Field data:

I've pushed some commits that added paragraph info:

jenlampton commented 3 years ago

I've pushed an update that adds views data, and ads color coding. Things that need to be changed before an upgrade are red (error) and things that could use a review are yellow (warning).

jenlampton commented 3 years ago

I've added a "todo" list to the top of this form, but now I'm wondering if having it right there is best, or if it should be provided by a separate submodule?

Originally I was thinking having it here could be helpful, as it would inform people in the "evaluation" phase what to do during the upgrade. But now I'm wondering about that... could use some input!

jenlampton commented 3 years ago

I've now also added three sections for modules: core, contrib, and custom. Each shows enabled projects, and suggestions about how to handle each one:

Core: