Propose user flow & entity model

Nice idea. I don't think we should be adding any entity as we are leveraging the sitewide_alert entity. I could see adding fields to that entity if we wanted to account for the options:

• a checkbox to allow choosing "no icon"
• a checkbox to allow choosing "slim"

This would be in addition to already adding
field_heading
field_weight

First draft of a entity model just mapping out the basics of the existing Sitewide Alert module to confirm my understanding https://app.mural.co/t/civicactions3117/m/gratitudegarden1406/1744213980...

Second draft, now with proposed new fields and blocks in pink https://app.mural.co/t/civicactions3117/m/gratitudegarden1406/1744213980...

Bonus points for providing visitor access to make it open :)

I saw Steve's comment in the Mural document on the complexity of adding an "Alert Type" field and think I understand his counterproposal, but I want to verify here.

If I'm not mistaken, Steve, you're suggesting that we add all of the USWD styles to the "Alert Style" field and forego adding an "Alert Type" field. The implementation would look something like this on the module configuration screen:

For the user creating a sitewide alert, they would see something like the following:

skyriter, yes exactly.

I think DavidmPickett's proposal is superior by splitting it up into 2 fields (style and type). My main concern is largely based on fear of not being able to fully anticipate existing scenarios of people already using sitewide-alert that are then just adding this module on top of it. We are already courting trouble by looking at how to interweave our config into existing config. This plan adds another layer on top of that.

If this were a standalone module I would have no concerns about Dave's content model as it is really solid.

Decision made to use Alert "style" only and not introduce "type."

Diagram created and decisions documented.