-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Untangle My Home #95386
Comments
Just to confirm, the idea here is to leverage the WP dashboard wholesale, with custom widgets for much of this here in My Home? |
@richtabor yes. We consider the My Home screen redundant and confusing in the Classic wp-admin interface. In addition, it's built on Calypso which we want to remove from the wp-admin interface experience. This project is to move some My Home components into wp-admin dashboard widgets. |
I don't think you're heading towards success with this approach, and problem-solving purely from a "WP Classic" perspective feels narrow. WP Classic is something we'll want to have across all sites, not just a self-selected few, so solutions should be solid. You're planning to take all this: Launchpad tasks And add it here: What's the point of all those widgets combined then? What was the go of My home that you're carrying over to dashboard? I could visualise the end result here but I'm sure it would look very hectic. :-) Alternatively, I'd suggest:
|
@simison we have a Feedback Request post. I've copied your feedback pekYwv-4JJ-p2#comment-4279 to keep discussions in a centralized place. |
Support References This comment is automatically generated. Please do not edit it.
|
Thanks! |
Why not? There's certainly things that can be combined and organised in such a way that it looks good and clear. For example Daily prompt could be extending quick draft. Should quick links be there in the first place? Why are they not in the main menu? Site Health status could be removed (cause we manage that), and replaced with general/launchpad tasks. Etc. Eventually we'll want to align with the WP admin redesign and help out there instead of doing our own dashboard. |
I had the same thoughts as Ella. Additionally:
We need to keep the efforts to refresh onboarding in mind here, but I think it's worth exploring a design that consolidates My Home with the wp-admin Dashboard. I have some ideas and will share soon :) |
Design explorations from @nuriapenya, somewhat touching the point of splitting launchpad/onboarding mechanisms separately from the dashboard itself:
|
Here’s a preliminary draft focusing on the overall user flow rather than fine-tuning the design of individual widgets. I recognize this iteration isn't polished, but the priority for now is leveraging as much existing technology as possible. We can refine the finer details after agreeing upon the flows. Building on the onboarding work @nuriapenya has been exploring, the following screenshot illustrates what a user might see on the Dashboard immediately after signing up. The page header is reused from ![]() To re-iterate, I'm not concentrating what the individual steps should be, just the overall flow and general composition. In this case each incomplete step in the widget can be expanded / collapsed, likely with one open by default. As the user works through each item they're marked as Once the user completes all tasks within the ‘Site Setup’ widget, it automatically disappears, and the user is redirected to the Main Dashboard. For developers or experienced users (or just folks who dislike setup wizards), the ’Go to Dashboard’ link provides a shortcut to skip directly to the main Dashboard. If they choose this option without completing the setup, the ‘Site Setup’ widget simply reappears alongside the other widgets in the main Dashboard. ![]() From here, users can finish setup tasks at their own pace or hide the widget entirely via Screen Options. Widget visibility should dynamically adapt based on onboarding responses and other contextual factors. If a user hasn’t registered a domain but has completed relevant onboarding steps, we might display a widget encouraging them to register one. Similarly the ‘Learn…’ and ‘Grow…’ widgets may only be visible after the site is launched: ![]() Ultimately there is a lot of scope to define different widget configurations based on user responses during signup, and the completion of steps during the onboarding tasks. If this proposal makes sense we should continue to discuss that, and iterate on widget designs. Changes OverviewMigrated / Consolidated
Removed
Hidden
Let me know what y'all think. |
Loving those @jameskoster 💎 some impressions around the Launchpad experience for wpcom users: If we were to build this tomorrow, the contrast between the onboarding signup screens and the wp-admin UI would be quite noticeable. I am aware of the admin redesign and so on, but for now, UI difference could create some distraction/familiarisation issues: Re: Inline task completion: Part of the Launchpad mission is to guide users and help them discover where things live. If we have a lot of inline actions, people might miss completely how to do them again at another moment once the launchpad is gone. That being said, I really like how you gave context on what each piece is important - something we currently miss. I guess this is a more generic problem to solve but having so many widgets is overwhelming. Significantly since the 3-column layout does not really help to give a sense of hierarchy.
Maybe these widgets appear only in the area they belong to? Do they have an item in the navigation? |
Why are we moving all of a sudden to inline task completion? Where has this been discussed? I'm not sure I like this departure from the current experience. IMO it's good that it links to the section on pages where the user will find them later (or can even go back to with browser history). This is also making untangling it unnecessarily complex. We should remember that this isn't part of the default WP experience, so I'm not sure if adding more bells and whistles at this point in time will help us. |
We discussed this a bit on Slack, summarising here; while I think there are some benefits to inline task completion, we agreed it was something to explore later. I'm going to continue iterating on the widget design.
My feeling is that it is more economical to use existing wp-admin design patterns as much as possible. |
Here's another design update. Stripped back, and hopefully approaching something actionable. Pre launch![]() The Site Setup widget body is updated to better resemble a task list. Inline task completion is gone; each task links out to the relevant destination instead. The tasks reflect the current ones found in the My Home launchpad, but this will most likely change quite soon. I'm keeping in touch with @nuriapenya about that. Primary buttons are replaced with secondary ones to reduce the fight for attention. Quick Draft includes the writing prompt, with actions to cycle through options, respond, and view other responses. ![]() Site preview is combined with Site Management Panel. Customize Your Domain and Support widgets still need design, they're next on the list. Post launch![]() Once the site is live the Site Setup widget is hidden, and the Learn / Grow / Stats widgets appear. |
@jameskoster Nice, this looks great, thank you!
No strongly held opinions of course. |
@ellatrix @jameskoster could you update this issue description with the new details, and add sub-issues as needed? 🙇♂ |
I added the latest designs to each sub-task. Let's continue to discuss therein. |
February 5 UpdateThe team has been recreating individual features of My Home in the wp-admin dashboard. Done
Next |
Important
Project Thread: p5j4vm-4Yc-p2
Current PRs:
Brief
To remove the “My Home” page in the Classic wp-admin interface and relocate its features either to the Site Management panel or as widgets in the wp-admin dashboard.
This change simplifies the user experience by addressing the redundancy between the “Dashboard” and “My Home” pages. Having two central hubs creates confusion, so we propose consolidating functionality into the Dashboard to better align with the core WordPress experience.
Visuals
Plan (to be confirmed)
The text was updated successfully, but these errors were encountered: