Oops we forgot about this one! Delivery options on the editing screen

[connorscarolyns]

We have three options here:

• 1 remove the purple bar and modal entirely
• 2 remove the delivery option radios from the list
• 3 We can present the info more like the publishing list & add a link to settings

@anikbrazeau @samsadasivan @timarney @Abi-Nada

[timarney]

Can we just remove the modal / "more" button and just keep the "purple bar" / quick select ?

---

Noting the current:

Like the form purpose I didn't add all the API stuff to this dialog. If an API key exists I do hide the delivery option.

[connorscarolyns]

If we keep the bar, we could remove the options to select anything (just show what is selected) and direct people to the settings tab with the button rather than open a modal.

[anikbrazeau]

I think we could probably remove the modal without losing anything? The specific settings (classification and delivery method) are now highlighted on the publishing checklist, which I don't think they were when we added this originally.

I also wonder how many folks chose branding from the purple bar versus in settings, it might be a bit redundant to have it in both spots especially given it's really a one-time choice and shows up on "Test" page with the preview as well?

[timarney]

I think we could probably remove the modal without losing anything?

I agree

[timarney]

PR to remove

#4776

This feature has always been quite hidden / tucked away under the ... button.

This will help on the App maintenance / testing end. All of the functionality + more is available under settings.

541 lines of code remove in that PR.

[timarney]

@connorscarolyns @Abi-Nada

Maybe 👍 before I merge that PR.

[Abi-Nada]

The PR LGTM! I agree, we've talked about the redundancy of that modal for a while now.

Before we merge, flagging to @srtalbot for visibility

[connorscarolyns]

When we added the administrative purpose, which has no default and forces the user to go to the settings page, the original problem this bar was created to solve resolved itself. Which was to surface those settings before the user could publish.