You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to create a simple wizard "scenario" that lets users choose which features and items to setup.
We can use a hook form alter to add the extra item to the list of scenarios on the default chooser in the DF install. This would just take us to the wizard form.
The form can simple list the features to enable - this would be df_tools modules like for content types, blocks, LB, etc. Maybe a choice of theme install and admin theme color scheme to round it out?
It doesn't need to be overly complex right now. Mostly we just want an example of how one might build a customizable installation wizard for customers to see.
The text was updated successfully, but these errors were encountered:
👍
This is a great features that would allow us to also demo a Site Factory with a kind of "App Store".
Instead of going to the boring module pages, following this wizard for features enablement (≠ of module, as the wizzard might enable multiple modules and import configs behind the scene) could really be a great showcase of real factory, used entirely by the customer without help and still in a flexible way.
Adding to this cohesion for frontend, and you have the ultimate custom (=PaaS) factory possible… :)
We need to create a simple wizard "scenario" that lets users choose which features and items to setup.
We can use a hook form alter to add the extra item to the list of scenarios on the default chooser in the DF install. This would just take us to the wizard form.
The form can simple list the features to enable - this would be df_tools modules like for content types, blocks, LB, etc. Maybe a choice of theme install and admin theme color scheme to round it out?
It doesn't need to be overly complex right now. Mostly we just want an example of how one might build a customizable installation wizard for customers to see.
The text was updated successfully, but these errors were encountered: