Enabling module and placing Masquerade block repeatedly slows testing unnecessarily
Masquerade block is placed in different places on different sites - often on page bottom
Proposed resolution
I propose we enable Masquerade module by default
Placement of Masquerade block, to reduce clicks during testing, should be at top of /admin/people
Block placement should be on Claro theme - /admin/structure/block/list/claro > Content - see screenshot below
Rationale for proposed block placement
Putting block at page bottom requires extra scrolling whenever identity change needed, put it at top of page for no extra scrolling
Masquerade during testing often requires finding a user with certain roles, by placing Masquerade block on /admin/people, it is easy to see individuals and roles with a quick scroll down and back up
Installing the module (and placing the blocks) on Campus Web Services' starter site (which would effectively make it installed by default by most new sites created by Campus Web Services) wouldn't require a change to Quickstart. We'd just to update that site
We could consider making a change to Quickstart to make the module installed by default (on all new Quickstart sites) and have the blocks placed by default
I'm going to update this issue to be a proposal to make those changes to Quickstart.
Problem/Motivation
Proposed resolution
Rationale for proposed block placement