When we replace home with dashboards, we'll no longer have a default home page to show administrators when they first login during setup.
On the balance, I think this is probably good thing, since the current default home page is not very useful, especially on a fresh install.
Two possible approaches:
# Just automatically build a "reasonable" default dashboard and install it on startup.
# Or, do something more onboarding/setup-focused.
(1) is straightforward, but a bit messy technically (for example, we're rarely going to test it -- especially if it's only on the install workflow -- and it's hard to unit test, and it's generally worse to break something on setup/install than elsewhere). It also won't be a very good first experience (everything will be empty) and it will have all the issues the current homepage does (being an OK fit for a lot of users, but a good fit for very few).
I'd like to experiment with (2), and build something that provides a more structured setup workflow for administrators, and guides them through setup tasks. Particularly:
- Set up authentication (there's a small hint about this in setup issues, but it could be expanded on);
- configure settings (there are almost no pointers to this);
- install/uninstall/pin applications;
- build a dashboard to replace this workflow.
And then maybe some general links to "learn more about tasks", "learn more about code review", etc.
Generally, I think we've had good luck with the "X unresolved setup issues" workflow, and want to try expanding that into onboarding -- the idea being "Quest Tracker" (optional, asynchronous, random-access, non-modal), not "Wizard" (sequential, mandatory, modal).
I think we'll //also// need/want some degree of dashboard templating or prefabrication, but can build that in a more tailored, testable workflow.