MC -> Paste: Full Page Modal

[ceyerkes]

Hello! I'm in the process of gathering more info on composable components that exist in MC but don't currently exist in Paste.

Full page modals are used extensively in MC in editing flows, as well as in the design library (screenshots). Instead of proposing a Paste-ified version of this component, I wanted to check in with the team to see if there are any other recommendations for this type of pattern.

[SiTaggart]

👋🏼 Hi!

Yeah, this is a bit of a tricky one really, because we really struggle to justify it when we look at the reasoning behind the need.

Most folks tend to give one main reason for a full page modal, which is keeping context with the action you were just performing or where you came from. The problem with that is in two areas:

1. If it's modal you can't access or use the information that you require context from due to the nature of modal dialogs. It renders the content beneath inert and out of reach.
2. If it's full screen you can't see the content you require context from

So really all you need is a quick way to go back to the screen you were just on, and that often just feels like a page navigation problem, rather than a component problem.

So we've, up until now, really only suggested making it a page. A normal, everyday page, that you navigate to like any other, and give them a prominent, easy to fine navigation action that takes them back to exactly where they were.

Are there any other reasons why that wouldn't work for you in this context?

[ceyerkes]

Reopening this discussion on full page modals in the context of an image editor.

I'm currently working through 3 image editor designs:

Wide Modal (current Paste)

Extra Wide Modal

Full Screen Modal

I completely understand avoiding full screen modals for the 2 reasons @SiTaggart mentioned above, but I think there's a case for making an exception for a focused editor flow. The team is leaning towards Extra wide and full screen, but would appreciate any feedback on these when you have a sec, thanks!

cc: @serifluous

[gloriliale]

@ceyerkes Was there a particular reason for not wanting to use the first option? I'm mostly thinking of how it works well for wide images like the one in these examples, which the other options cut off. Also it allows you to see the same amount of filtered examples.

[ceyerkes]

@gloriliale we could definitely change the dimensions of the preview to be wider in the 2nd and 3rd, this is just a quick mockup - there's plenty of room on either side. The first example gives us significantly less preview room (350px square), which is why my PM and I like the 2nd and 3rd options better (600+px square).

[ceyerkes]

Side-by-side with image sizes increased on full and extra wide modals:

[serifluous]

Rounding out the convo here: @kelseycavitt, @ceyerkes, and I met, and we landed on a solution to use the existing Content Editor/UI page and swap out the Email preview for an image preview/editing—so no modal needed.

Closing the discussion again for now.

[ceyerkes]

Reopening this convo - @cfree has concerns around not being able to influence the actual URL routing within the application (he can explain this better) and is recommending the big modal over the full page:

[kelseycavitt]

@ceyerkes Hi, can you elaborate? Is he wanting a dedicated "page" so there is a URL?

Also, can @cfree ?