- Issue created by @mandclu
- ๐ฎ๐ณIndia prashant.c Dharamshala
Like the WordPress also does. It has many tabs but we can have only something like the "Suggested" section.
- ๐บ๐ธUnited States chrisfromredfin Portland, Maine
One vision I have had for a while is to display a "post-apply" modal for either modules or recipes. In this way, we tell the user the things they need to do to configure the project they just installed. Even if that's not a full wizard (i.e. "Enter your Google Analytics id here: [____]") it could at least be "For this module to function, you will need to enter your Analytics ID here: https://your.site/admin/config/whatever").
I think we could utilize this same "post-apply modal" to show what a recipe suggests, maybe.
- ๐จ๐ฆCanada mandclu
I believe I have see talk about a config action to add dashboard items from a recipe, maybe something along those lines could be a stopgap until there's a way to have a more sophisticated display of related recipes in project browse
- ๐ฉ๐ชGermany rkoller Nรผrnberg, Germany
But there is one significant problem to consider in regard the idea of providing some sort of post apply modal as suggested in #3 โจ Allow a project to suggest other projects, present in UI Active . If you add and install a single module that post apply modal pattern works, but how do you handle the case of 2 to x number of modules installed at once, which is the likely case with the batch functionality being the only way to install modules - having a chain of post apply modals in a row seems suboptimal.
- ๐บ๐ธUnited States chrisfromredfin Portland, Maine
Re the "chaining" of wizards... we already do this in core - you can add multiple fields to a view in one go, and then you configure each field in the order you added them. I would propose the same for the post-apply modals.
- ๐บ๐ธUnited States phenaproxima Massachusetts
Honestly, I would not have this be particularly complicated; maybe we should just add a new "related projects" field to the Project object (really just a collection of links), and send that to the frontend to be displayed in the detail modal. Wizard-chaining (I swear I just heard some metal guitar when I wrote that) or other tricky stuff seems somewhat unnecessary.