Wow, this is just awesome, started testing this plugin today and looks really powerful! Thanks a lot for sharing this with the community and keeping it updated @angus and @merefield
Really look forward to conditional rules for the post builder if it’s still planned, that would be a fantastic addition and really unlock a lot more potential uses.
Something else that would be cool is an option to override the New Topic button to send users to a wizard. I’ve thought of a few ways this could be implemented with varying complexity.
Global Override ‘New Topic’ Button
Globally send the user to a single specified wizard, regardless of if they are on the homepage or a category. Looks like either the logic for the category could be sorted in the wizard itself, or a simple wizard like the welcome example could be used to route the user to the correct wizards for their new topic.
The only downside to the global override approach would be that all new posts would have to go through a wizard, but I don’t think that’s a big deal at all. Some wizards could be be more or less a simple composer editor if needed. I imagine this should be possible without it being directly supported in the plugin too, just not really sure how that would be done though.
Override ‘New Topic’ Button on a per Category Basis
Allow assigning different custom wizards for the New Topic button for:
- The homepage (ideally using a simple wizard to route the user to an appropriate wizard for their topic).
- Each individual category (if none is assigned, then the regular composer will open).
An alternative, but likely significantly more complex approach, would be keeping the regular composer support when the New Topic button is pressed. But if a user selects a category or subcategory that a custom wizard is assigned to, closing the composer and sending the user to the specified wizard.
E.g. On the Pavilion site the New Topic button is disabled in the open source parent category as well as the bug reports and feature requests child categories. It looks like selecting those categories are also disabled in the composer if I open it from a different child category within the open source parent category. I’m guessing this is to ensure using the wizard for topic creation in those two child categories.