Skip to content
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

Home Screen: Checklist step asks users to add a menu — when one is created by default already #44240

Closed
ianstewart opened this issue Jul 16, 2020 · 6 comments · Fixed by #52077
Labels
[Feature] My Home The main dashboard for managing a WordPress.com site. [Size] XS Tiny sized issue [Type] Bug

Comments

@ianstewart
Copy link
Contributor

The title of this issue covers the issue but to reproduce …

Create a new site.

Note the instructions about the checklist in the menu.

image

Follow instructions and visit the Customizer.

image

Note that a menu with multiple pages already exists by default.

cc @lcollette

@ianstewart ianstewart added [Type] Bug [Feature] My Home The main dashboard for managing a WordPress.com site. labels Jul 16, 2020
@github-actions
Copy link

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

@ianstewart
Copy link
Contributor Author

This issue can still be reproduced.

@michaeldcain
Copy link
Member

I believe we should be able to check if a menu is assigned on the user's site and conditionally switch the heading to say "Edit your site menu"

@simison
Copy link
Member

simison commented Mar 10, 2021

There are quite a few things going on here simultaneously, and I think the incorrect copy is the least of our problems:

  • How customers know where to create or edit their site's navigation? I believe the current checklist item is mostly "patching" this confusion.
  • On the flip side, while they now know where to edit the menu, editing navigation is really complex. It's adding to the confusion by introducing this step pretty early in the site creation, and hence we thought to just remove the whole step (My Home: remove 'edit your menu' checklist item  #47334), or at least move it down in the list (My home: swap "create a site menu" and "update your home page" order #49706). On the other hand, removing would lose the guidance.
  • Lastly, it's prompting to create a menu when one already exists. We could either edit the copy or remove the whole step.
  • We also now have themes (blank canvas) and designs that don't have a header/footer (and hence navigation) at all. We don't guide how to enable header/footer/navigation (nor relation between those) in any way.

Non-risky actions I see are:

Anything else feels like we'd potentially increase the confusion accidentally. Does that make things better while we wait for FSE sites, which of course will change everything for this task completely? Are there other simple actions we could do to make this much better for soon-to-be-legacy sites? @olaolusoga & @ollierozdarz.

cc @autumnfjeld just to follow the convo at this point.

@roo2
Copy link
Contributor

roo2 commented Mar 15, 2021

We just bumped it lower in the list (#49706)

It looks like it is trivial to change the copy to "Edit the site menu" in https://github.com/Automattic/wp-calypso/blob/trunk/client/my-sites/customer-home/cards/tasks/site-setup-list/get-task.js#186

@ollierozdarz
Copy link

Non-risky actions I see are:

Bump it lower in the list (#49706)
Change copy in this scenario to "edit the site menu" if it's trivial.

These feel like the correct course of action to me, @simison 🙂. A quick and iterative win while this gets more thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] My Home The main dashboard for managing a WordPress.com site. [Size] XS Tiny sized issue [Type] Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants