Skip to content

Enhance the Publishing flow #7602

Closed
Closed

Description

@karmatosed

Update 28 June 2019 (exactly one year after originally opening!) by @sarahmonster:

This issue is a long discussion about the overall experience of publishing a post and is now being used as a tracking issue to. To contribute ideas, feedback, or just follow along with the conversation, please use the following issues:


Original issue text from 28 June 2018 by @karmatosed:

Right now on publishing the experience comes to an abrupt end. For example:

2018-06-28 at 11 42

Whilst the content of the post may not mean we want to celebrate with balloons and ribbons the publishing, having something that doesn't just stop at this empty end is needed.

Preview looks like this....

2018-06-28 at 11 55

A few ideas could be to have an animation such as here: https://www.wired.com/2013/12/a-sandbox-for-experimenting-with-animated-typography-built-by-a-google-designer/.

This has been talked about in other issues and it's worth creating one here to just focus on this and explore. Along with adding some flourish to this page of engagement also looking at the format. This is pretty flat as an end to the experience. Beyond any animation this screen showed above could do with some iterations itself.

Could perhaps bringing in a better previewing to this all also be wrapped in? Thinking about this in stages may be the best, what can we get in for phase one. Then maybe having a preview modal or something on preview could be brought in later phases. I think it's worth in designs exploring freely then distilling back.

Worth noting that exploring things like having this across all devices is important. What could be created that adapts well?

Activity

  1. changed the title [-]Enhance the publishing flow[/-] [+]Enhance the Preview and Publishing flow[/+] on Jun 28, 2018
  2. sarahmonster commented on Jul 9, 2018

    @sarahmonster
    Member

    Since there's a rather a lot at play here, it might make sense to split these into two different issues. This is how I currently see these two improvements breaking down (and I have questions!):

    1. The post-preview-button loading screen ("please wait, generating preview") that appears when you click on the "Preview" button whilst working on a post. Since this screen will appear for a varying length of time for different users, we may want to consider what we can do to make it interesting or exciting. A fleurishy animation could be one approach, or we could try an empty-state animation to help with perceived loading time.
    • Is the primary intent here to improve the perceived loading time, or to add interest to the experience?
    • How much time (range) do we expect this screen to be visible for?
    • Do we also need to design for a potential failure? I've seen a few cases (my local install is currently doing this) where the preview screen appears and the post preview never goes away.
    • On a technical level, do we have access from this component to the post content or post meta?
    1. The post-publish-panel component that appears after you've published a post. Right now, a sidebar pulls out and says the post is now live, with a "what's next" section offering two options: 1. Visit the post and 2. Copy the link. This is pretty anticlimactic, so we'd like to give it more character and sense of purpose, whilst avoiding being too congratulatory or cutesy.
    • Will this sidebar panel be extensible by plugins?
    • Why have we opted for a sidebar here, rather than a modal, notification, or full screen?
    • Do we have any research on what action users want to take once they've published a post? (I am guessing that some users will want to ignore any prompts and get on with something else, whilst other users would like to proofread their post in-situ and probably share it to social networks, send it out via email, tweak it for SEO purposes, etc, but this is purely speculation.)

    I'm having a comb through issues to surface history and prior conversations around these two experiences as well, but if there are particular discussions that it'd be helpful to read, I'd appreciate a link or two as well. 😸

  3. karmatosed commented on Jul 9, 2018

    @karmatosed
    MemberAuthor

    Thanks for tackling this one @sarahmonster. I am totally into splitting into issues and leave that up to you if want to. I do think it's perhaps the same flow but totally could be.

    Is the primary intent here to improve the perceived loading time, or to add interest to the experience?

    Both! Mostly improving perceived loading time but also engaging is good here.

    How much time (range) do we expect this screen to be visible for?

    This can vary but usually isn't long at all, it just 'could' be. Also having anything is better than even a flash of white blank screen.

    Do we also need to design for a potential failure? I've seen a few cases (my local install is currently doing this) where the preview screen appears and the post preview never goes away.

    This used to be a bug, it shouldn't be anymore... if it still is lets get it fixed over designing around a flaw.

    Will this sidebar panel be extensible by plugins?

    Yes.

    Why have we opted for a sidebar here, rather than a modal, notification, or full screen?

    So it can be extended and it's a better experience than a modal, there also doesn't need to be a full screen take over. Right now let's stick with sidebar.

    Do we have any research on what action users want to take once they've published a post? (I am guessing that some users will want to ignore any prompts and get on with something else, whilst other users would like to proofread their post in-situ and probably share it to social networks, send it out via email, tweak it for SEO purposes, etc, but this is purely speculation.)

    Most seem to want to see post or just carry on. It feels like a 50/50 split from observations.

  4. changed the title [-]Enhance the Preview and Publishing flow[/-] [+]Enhance the Publishing flow[/+] on Jul 12, 2018
  5. sarahmonster commented on Jul 12, 2018

    @sarahmonster
    Member

    I'm splitting the preview loading experience into #7922 and will leave some ideas there, so as to keep this thread focussed.

    Benchmarking other publishing flows

    Before making recommended changes, I looked at what other services are doing, to get a sense of how it's handled elsewhere, what works well, and what's not so great. It turns out there's a wide variety of experiences offered by different services.

    WordPress.com

    2018-07-10 13 28 28

    Two presses to publish, then redirects to post itself, with a "Post published on [site]!" dismissible notification and a top header bar that allows for previewing the post at different breakpoints, going back to edit the post, and copying the link. Updating a post just prompts a notification whilst remaining on the same screen. Very similar to the current Gutenberg experience, but a bit more polished.

    Wix

    2018-07-10 14 07 24

    One button with a dropdown. Pressing publish opens a (dismissible into the future) modal that offers to share to social media (email, Facebook, Twitter, LinkedIn).

    Medium

    2018-07-10 14 15 01

    Publish button pulls up a pre-publish panel with some tips (add tags, add an image, share on social media) and a second publish button (below!). Pressing the second button redirects to the new post. (Post = "story")

    Ghost

    2018-07-10 14 42 25

    V similar to Medium, with a publish (indicated by a dropdown, not a button) then pulling up a post-publish panel that gives the option of "ready to publish your post?" + a post now/schedule for later option, and a second publish button at the bottom. Nice animation and use of icons on the button from publish > publishing > published. Also shows a "Published! View post" modal at the bottom left hand side of the screen, although it's super easy to miss.
    (Blog = "publication", post ="story")

    Hubpages

    2018-07-10 15 09 56

    This is a pretty terrible experience overall, and required a text message confirmation before it would publish. Once you finally get all that sorted though, you get a "Congratulations! You've posted your first article!" notification that also includes some info about their QA process, suggests to write another article ("Your new article is lonely: Create another article!"), and a copyable link to the article itself. (Two, actually.)

    Contentful

    Required a German version and a specific format for the title before it'd allow me to actually post anything. Uses a single "publish" button with a drop-down for more (change status.) Never actually got through the publishing flow, so who knows what happens at the end!

    Tumblr

    2018-07-10 15 28 08

    There's a button with some drop-down options (post later, etc). One click to publish ("post", in this case.) Clicking through redirects you to the main homepage/feed, with no indication the post published. (Where did my post go?)

    Blogger

    2018-07-10 15 30 57

    Uses a simple "publish" button. Redirects back to a post list. Gives me a whole slew of notifications, but nothing related to the actual post I published.

    Svbtle

    2018-07-10 15 36 27

    First you need to use the "save idea" button, then an additional menu area appears with settings, preview, publish button, and save button. Hovering changes the text to "publish now". Clicking through causes a modal ("You sure you want to publish now?) Clicking through makes the whole screen pulse green, then a bright blue "published" notification appears, + a link to view post.

    Livejournal

    2018-07-10 15 51 44

    Uses a drop-down "Tune in and publish" button (drop up?) that opens more options, similar to Ghost/Medium but with some button styling, rather than just the dropdown styling. Pressing opens the dropdown/up with additional settings (post to different journals, publish date, plus RSS, x-post, sticky, etc options), with a second "publish" button at the bottom. Clicking that then redirects to the new post.

    Pen.io

    2018-07-10 16 02 44

    Suuuuuuuper simple. Hit a publish button, your post (page) is published. No bells and/or whistles.

  6. sarahmonster commented on Jul 12, 2018

    @sarahmonster
    Member

    Suggested improvements to our flow

    For comparison, here's Gutenberg's current publishing flow in action:

    2018-07-12 09 30 10

    Here's my current thinking for how we can improve this flow:

    Pre-publish

    • I've already submitted a number of small changes and bugfixes here, mostly attached to Use Pre-Publish Panel for Tags and Post Format #7426
    • We could shorten the header text to read "Ready to publish?" instead
    • The pre-publish panel should be dismissible (either a pre-checked "Show this every time I publish" box or a "Don't show this again" checkbox) for power users who don't want to be forced to click twice to publish a post. I could see this being frustrating for people who publishing multiple times a day and just want to get on with it.
    • Giving a prompt to add tags is nice, but it could also be moved to post-publish, since it's not critical to the pre-publishing experience, which should be geared toward making users feel confident that they're ready to go for it and post.
    • We could improve the animation states of the publish button to show what's going on. (Ghost's is super nice, with the changing colours and icons.)
    • Double-clicking the button is a bit unintuitive. It looks as though there was originally a drop-down in the button here, so I may be missing some historical reasoning for the decisions here, but coming at this from a relatively green perspective, I think a better pattern here could be to have a visual indication that the publish button doesn't trigger an action, but rather pulls down a sidebar with additional actions. (So, a little drop-down icon.) Converting the sidebar here into an actual drop-down may help distinguish it from the settings sidebar, as well as connecting it more closely to the button from which it originates. (See also Improve pre-publish panel styling #7879.) Livejournal, Medium, and Ghost all follow this pattern and it feels the most elegant.
    • There should also be a secondary "Publish" button at the bottom of the the pre-publish panel, so you check all your settings, looks good, and then the final step is to press the publish button. At the very least, the interim Publish button should change state more noticably, so that it's clear a second click is required (see WordPress.com example).

    Post-publish

    • It seems as though, for most users, their next steps after publishing would be either to look at the post, or to go back to their post list and write another post. In either case, there's no value in abandoning the user on their edit post page—they're finished with this screen, at this stage. Since 50% of users want to see their post in situ, let's try taking them there directly, and saving them the click. In my benchmark testing, the flows that redirected to the post itself after publishing were the ones that felt the most inherently satisfying—it felt like I'd really done something, and I could see immediate evidence of that.
    • We could potentially use animation to highlight the shift from the edit screen to viewing the actual post. See Svbtle's flashing green border—I think this is a bit intense, but having a transition between pressing publish and being shown your new post could be really nice. We could show a short message "Great work! Let's take a look at your new post...." and have a brief
    • We could also use the post-publish area to help users get the most out of WordPress. I did a skim through articles with titles like "what do I do after publishing a blog post" to get a quick sense of what users want to do after publishing, and it seems like the biggest concern here is with getting that post out to others: optimising for SEO, sharing on social media, sending via email, checking stats, reading comments, etc. Since these functionalities are provided by plugins rather than core, we can't directly link to them here, but we can help nudge users toward them.
    • We could provide a checklist for "What's next?" to offer people some suggested steps to promote their post. (And a link to write a new post, as well!)
    • We could also feature a series of (potentially rotating, always dismissible) tips or ideas for promotion here. ie, "Did you know? The best time to send out an email is 4pm. [Read more]"

    On "hurray!"

    The first time you publish a post is very different from the hundredth time you publish a post. How do we account for these varied experiences?

    Should WordPress commemorate this in some way? We could consider congratulatory milestones: published first post, published six posts this month, written x words, etc. Nothing too confetti-laden, but perhaps a simple message in the post-publish screen: "Great work on your first post!"

    This would be a nice way of putting a bit more emotion in the interface, but we don't want to annoy or disrupt users. Can we note important milestones without potentially seeming tone-deaf if someone's writing a blog for therapeutic purposes, or about a traumatic subject?

    Research

    I've tried to approach this with the intention of being as helpful as possible. How do we help users get the most from their new post? What do they want to do immediately after publishing a post? I looked for research into this but couldn't find anything specific to "what do users want to do after publishing a post?" Thus, my recommendations here are mostly based on guesswork, assumptions, and/or looking to what others are doing in this space.

    I think it could be super beneficial to do some user testing here, both of the before flow and the after flow. My thinking is that it would be ideal to test it with the following types of users:

    • someone who posts many times a day
    • someone who is new to WordPress
    • someone who works for a news organisation

    Do we have a pool of users anywhere to test with, or have usability testers typically been recruited on a per-test basis?

    Next steps

    I'll work on some mockups for this suggested flow next, but I'd welcome any ideas or thoughts on the suggested approach here!

  7. karmatosed commented on Jul 12, 2018

    @karmatosed
    MemberAuthor

    This is all really great @sarahmonster as an exploration, thanks. Let me dig into some responses.

    • The animated button on wordpress.com feels super effective.
    • There is something 'yay' about the Wix modal.
    • I don't dislike Medium's drop down but my concern as mentioned in another issue is what happens to extending this with plugins? This totally may be an issue we decide is ok though. I'm down with exploring.
    • Hubpages is intense....
    • Tumblr makes me scared I lost something....
    • Svtble feels super disjointed.

    Now onto your improvements to respond. Firstly some super interesting ones here, thank you for your suggestions already there.

    The pre-publish panel should be dismissible (either a pre-checked "Show this every time I publish" box or a "Don't show this again" checkbox) for power users who don't want to be forced to click twice to publish a post. I could see this being frustrating for people who publishing multiple times a day and just want to get on with it.

    This is interesting. How do you get it back if want to change mind?

    Giving a prompt to add tags is nice, but it could also be moved to post-publish, since it's not critical to the pre-publishing experience, which should be geared toward making users feel confident that they're ready to go for it and post.

    How would you suggest this?

    We could improve the animation states of the publish button to show what's going on. (Ghost's is super nice, with the changing colours and icons.)

    Yep :)

    I think a better pattern here could be to have a visual indication that the publish button doesn't trigger an action, but rather pulls down a sidebar with additional actions. (So, a little drop-down icon.) Converting the sidebar here into an actual drop-down may help distinguish it from the settings sidebar, as well as connecting it more closely to the button from which it originates.

    I'd love to see your explorations there considering the extensibility complexity.

    There should also be a secondary "Publish" button at the bottom of the the pre-publish panel, so you check all your settings, looks good, and then the final step is to press the publish button. At the very least, the interim Publish button should change state more noticably, so that it's clear a second click is required (see WordPress.com example).

    I am torn about this, I don't think double buttons work in this sense. Maybe explore other things first? I'm not ruling it out as much as want to see the other impacts then loop back.

    I'd love to see you explore all your post-publish points. Same goes for your 'hurray' points, love to see what you come up with from those.

    Thank you for taking such a considered approach, look forward to see where this goes.

  8. johnmaeda commented on Jul 16, 2018

    @johnmaeda
    Contributor

    Can we note important milestones without potentially seeming tone-deaf if someone's writing a blog for therapeutic purposes, or about a traumatic subject?
    +1 to this @sarahmonster -- the idea of "Yay!" etc is well-meaning but ill-fitting in all cases.

  9. sarahmonster commented on Jul 17, 2018

    @sarahmonster
    Member

    I've mocked up two different solutions to this problem, exploring different approaches to various different parts of the problem. I understand that this may, in a few cases, be re-introducing patterns that have been decided against in a previous iteration, but given that a great deal has changed since, I figured it would be good to approach it with fresh eyes.

    I've designed this from a mobile perspective first in order to ensure that we prioritise for the simplest possible display first. I've just started with two different explorations, in order to get some ideas out there, but I expect we'll combine some of the component elements as we iterate on this flow.

    Animations and UI elements are obviously pretty mockuppy at this stage! 😜

    Variant 1

    2018-07-17 03 54 15

    mock1

    Prototype: https://automattic.invisionapp.com/share/USMZOBPWMHZ#/

    Here, I've split the "publish" button to allow for two different actions here, depending on how trigger-shy the user is. Clicking the main part of the button publishes the post immediately, and clicking on the drop-down icons pulls down the pre-publish panel, now as a popover container instead of a sidebar element, so it feels more consistent with other patterns. (See conversation in #7878, and my understanding is that this may also help with some accessibility concerns.) I've also dimmed the background to reduce noise and improve focus.

    This one makes use of a secondary publish button in the popover, but either button would work to publish the post. My thinking here is that if you're opting to go through a pre-publish check by clicking on the down-arrow portion of the button, you want to actually read through those checks in a (relatively) linear, down-headed sort of fashion. Putting a button below all that would be a logical place for people to expect it, and we don't need to design in this case for the impatient user who just wants to click through and get it over with, since they can avoid the double-click on the button altogether.

    The focus here is on the post-publish panel, which appears to give tips and next steps. I expect that plugins would make heavy use of this and would likely be responsible for adding a lot of the functionality that people would want post-publish (fine-tuning SEO settings, sharing on social media, etc). I've tried to focus on what we can do with the out-of-the-box experience to make it feel like an accomplishment, without trying to be too celebratory or cutesy, as well as to guide the user in getting the most from their post.

    Variant 2

    2018-07-17 10 41 07

    mock2

    Prototype: https://automattic.invisionapp.com/share/7FMZOEYZST6#/

    This variant uses an alternate iteration on the "publish" button, more aligned to the WordPress.com solution. It does mean it's a bit harder to decide on-the-fly if you want a pre-publish checkup, but the panel will be more discoverable for more users. It also means we'd need to store a setting somewhere to allow users to opt out of the double-click publishing experience, which I think we'd need to store under "Settings" in the ellipses bar menu.

    In this, your post is highlighted more immediately after publishing, but it feels less like something important's happened. It is, however, a lot easier to review your post for any issues, then work on any post-publishing follow-up actions, like adding tags or sharing on social media.

  10. karmatosed commented on Jul 18, 2018

    @karmatosed
    MemberAuthor

    Thanks for all this work @sarahmonster, so much in good way to process.

    First, I am very pleased to see a focus on mobile first. I do wonder as an over-arching point how does this work if someone extends the sidebar? Maybe could you also explore a full sidebar just as a comparison? Someone could have a few plugin that check things like SEO, tags, spelling and even have more options on publish like sending to social media. What would those look like as a stress case?

    First version:

    • I am not sure about full modal take-overs on desktop, this needs to be something to explore.
    • Thanks for showing flows and video, that's really helpful.
    • It feels somehow like there are a lot of steps in the first version. I think this is because it's split and not sure that's a bad thing but it's worth noting.
    • I wonder if the green publish is resulting in relying on color too much? I'm unsure but worth checking as that check icon seems a little lost.
    • I do like 'great work' as a phrase and think it's a balance over overly celebrating.

    Second version:

    • What would that flip animation be on desktop?
    • This does feel like it has some concerns for the publishing extensibility.
    • I kind of like idea it gets to the showing of your post, but I keep musing if this is always the action someone wants. It may be, I just am unsure.
    • I like the 'next steps' and think that type of nudge is a welcome push for interaction.
  11. mtias commented on Jul 19, 2018

    @mtias
    Member

    Closing in favor of #7922.

  12. 42 remaining items

  13. mapk commented on Jun 14, 2019

    @mapk
    Contributor

    Thanks for wrangling this, Sarah!

    Let’s try “Ready to publish?”

    It feels awkward to have a question as the label for a button. If I'm clicking a button, I'm performing the action it should be suggesting, right? I noticed Amazon has a "Proceed to checkout" label on their button. I wonder if that's kind of what we're doing here? Maybe, "Proceed to publish" or "Prepare for publish".

    Next, let’s switch the publish sidebar to a modal. According to our design guidelines:

    I'm on board with this! Good call. "It's also going to be a more consistent experience across mobile devices and larger screens." is a great point!

    A darker scrim is much better for focussing user attention:

    Yep! 💯

    I'd also recommend changing the wording on the publish button itself, depending on when the post is scheduled for:

    Future: Schedule post
    Past: Publish retroactively
    

    Good thinking. This little fix help reinforce the changes made too!

    Are tag suggestions here helpful, or do they belong instead in the post-publish panel?

    I think we can drop the tag suggestions. Let's try to keep the user's focus on the immediate things they need to check before commiting.

    let's treat it as a tracking issue, and try to split all the different improvements into a series of smaller tickets.

    I like that idea. Let's keep this issue updated with links to all the smaller ones.

  14. sarahmonster commented on Jun 27, 2019

    @sarahmonster
    Member

    Thanks for the feedback @mapk! I've moved your idea over to # 16342 for further discussion.

    I've now refined the original concept here based primarily on findings from usability studies and intuition:

    2019-06-28 01 05 54

    (Figma prototype and source)

    I've split these recommendations into component issues and have updated the original issue text here, so it's easier to find these linked tickets. We'll use this issue as a tracking issue, and discuss individual changes recommended on these tickets:

  15. karmatosed commented on Jul 4, 2019

    @karmatosed
    MemberAuthor

    @sarahmonster does this issue need keeping open if those others are being worked on? Just checking if we can tidy up this one?

  16. sarahmonster commented on Jul 4, 2019

    @sarahmonster
    Member

    Let's keep this open as a tracking issue—it's helpful to be able to find all the related issues in one place. Once those related issues are dealt with, we can close the tracking issue.

  17. sarahmonster commented on Aug 2, 2019

    @sarahmonster
    Member

    Circling back here, I've combined some of the conversations from #15847, #16127, #16342, #16308, #16311, #16310, #16327, #16341, and other publishing-related issues into a single, combined prototype. Some of the finer details are missing here (datepicker behaviours and improvements, error handling, editing dates and visibility directly from the pre-publish panel, surfacing visibility and publishing options in the document settings, the title block, etc), but it should be enough to get the broad strokes of the proposed changes here:

    2019-08-02 01 57 23

    Figma prototype

    Note that the transition between pre- and post- publish panels is still subject to change—more solutions illustrated in #16327. I'm not sure anymore if I'm leaning toward the dialog-snackbar-dialog pattern shown here, or the dialog-dialog-dialog pattern. That decision may be contingent upon accessibility and usability feedback.

  18. karmatosed commented on Aug 7, 2019

    @karmatosed
    MemberAuthor

    First, thanks for taking the time to create this mock walkthrough @sarahmonser. I do have a few points this brings to mind, some of them because of the recent explorations in full screen modal.

    It does feel a little disjointed as it goes between screens, the changes in height and spacing is a little jarring to the flow. I think it takes me out of the flow of publishing. I know I've been vocally against a modal here and I still feel in current version this leads to a weird ending to the writing journey.

    Looping back to the idea of a journey when you write, this is the end in some ways. I feel the modal takes me out of that and doesn't lead me to the celebratory high point. Just a thought to add to this. Personally, I wonder how this could change 'if' the full-screen modal @youknowriad proposes gets in. A few things I wonder about the modal:

  19. afercia commented on Aug 7, 2019

    @afercia
    Contributor

    I share the feeling that the size change of the modal through the steps is a bit confusing. That could be solved in many ways, including but not limited to the full-screen modal dialog proposal.

  20. jasmussen commented on Aug 8, 2019

    @jasmussen
    Contributor

    As the efforts here continue, and as the archive is getting increasingly buried and hard to browse, I thought I'd resurrect some of the thoughts we formed while designing the first iteration of the pre-publish flow. I present these only as historical context, not as a value judgement in favor of one design or another.

    The pre-publish experience is super important:

    • On a base level it serves as an “are you sure?” dialog, which is a valuable sanity check before publishing.
    • On a higher level it serves as a means to make the celebratory act of publishing your hard-earned words special.
    • On a meta level it is just enough friction to ensure that people think, even for a second, before actually publishing, which seems increasingly like the value a personal website can offer online discourse.
    • Finally it serves as a last minute checkup of metadata, which also provides a good API surface for third parties to hook into. This is especially important for users who dismiss the sidebar.

    We did learn as we went about the designs, that we wanted to be somber and neutral in this pre-publish dialog, as the words a user might publish are not always appropriate to celebrate. This is why we opted to not include too much colorful language or illustrations. This bit is a delicate balance.

  21. karmatosed commented on Aug 8, 2019

    @karmatosed
    MemberAuthor

    +1 to everything you wrote @jasmussen. I think with phrases like 'Great job' we have to consider what if someone is writing about a loved one that is no longer around, something personally traumatic.

    The pace and journey are essential to consider here.

  22. sarahmonster commented on Aug 8, 2019

    @sarahmonster
    Member

    Thanks for the feedback, everyone! It sounds as though I may not have yet landed on a solution that solves the problem at hand.

    Since there's been some lengthy back-and-forth in this issue (and others!) without landing on a good solution, it may help to take a few steps back and clarifying:

    1. What's the problem we're trying to solve?
    2. How will we know when we've landed on a solution that solves the problem?
    3. Are the suggested changes an improvement on the original/current solution, or a step backward?
    4. Are there any parts of the current publishing flow experience that aren't working for users? (Maybe everything is great?)
    5. Do we have any relevant data (qualitative, quantitative) that we can use to identify problems with the current publishing flow, or support our hypotheses here?

    Once we have answers to those questions, we can look to revisiting and/or closing out this issue and its component sub-issues.

  23. mapk commented on Aug 8, 2019

    @mapk
    Contributor

    The prototype really helps convey this flow! Thanks for doing this.

    The three-modal version shared here #16327 (comment) feels visually like the better way to go between the two choices. The user is in the modal flow, and stays in until done.

    As for the modal jumping around, I think it can be refined by fixing the top position of the modal and only changing the height? Or maybe animating through the modals would provide a better transition, similar to: #16327 (comment)

  24. brentswisher commented on Aug 24, 2019

    @brentswisher
    Contributor

    I have updated my Draft PR #16715 to be based on @sarahmonster's latest prototype if anyone wants to take it for a spin, I did make some changes detailed in the comments. It needs some overall design clean up, but it should allow you to experience what using a publishing modal "feels" like. I hope to create a branch that combines this and @youknowriad's full-screen modal early next week to give an idea of what that would feel like as well.

  25. karmatosed commented on Feb 4, 2020

    @karmatosed
    MemberAuthor

    This was brought up in design triage and for now, closing to review later in iterations. There is a lot going on with the flows right now which means letting that settle then look at everything holistically is a great plan. If someone still wants to explore they can as issues can always be reopened later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Needs Accessibility FeedbackNeed input from accessibilityNeeds Design FeedbackNeeds general design feedback.[Feature] SavingRelated to saving functionality[Focus] Accessibility (a11y)Changes that impact accessibility and need corresponding review (e.g. markup changes).[Type] EnhancementA suggestion for improvement.[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions