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

Pages: allow setting Homepage from the contextual menu without visiting Customizer or Reading Settings #42016

Open
lancewillett opened this issue May 8, 2020 · 10 comments
Labels
Pages [Platform] Atomic [Platform] Simple [Size] M Medium sized issue [Status] Needs Design Add this to PRs that need input from Design Triaged To be used when issues have been triaged. [Type] Enhancement [Type] Feature Request Feature requests

Comments

@lancewillett
Copy link
Contributor

Suggested change

Allow setting the initial option for choosing a page as static “Homepage” when the site is set to show the latest posts as the homepage.

Context

We want to empower site authors to not need the Customizer to build their site quickly and easily from Calypso.

We want to make sure they can learn via hints in the UI, and be empowered to make changes themselves.

The Issue

In the default state, WordPress.com sites show the blog feed as the homepage.

The following is what shows up in Site > Pages area in Calypso:

screen-shot-2020-03-02-at-07 45 12

Item A on the screenshot takes you to the front-end of the site. As a user, I might assume that this takes me somewhere I can change this behavior and set an actual landing page as the homepage, — but it doesn’t.

screen-shot-2020-03-02-at-09 02 06

If I want to change this… where do I go?

Answer A: Create a new page, and call it “Home”? Nope.
Answer B: Click on that icon A on the screenshot? Nope.
Answer C: Click on the three dots on the page I added to my site, and look for an option to “Set as homepage”, and use that to change this? Nope:

Question/Request

If not just placing the controls into the Pages contextual menu — even in the default state — suggest making at least a usability change.

Could we link to the appropriate section in the Customizer right here? Using the wording “Front page is showing your latest posts” to provide the link. Similar to what we have in My Home for editing menus.

Props @davipontesblog for starting this idea.

I don’t think this will solve all the confusion about having posts in the homepage or a static page, and this might not be an issue in the future as having posts in your homepage might rely entirely on static pages with a Posts block, but, for now, it could save a lot of headache and churn (“I wanted a website, not a blog!” said a frustrated user every once in a while in chat).

Thanks for considering!

@lancewillett
Copy link
Contributor Author

lancewillett commented May 8, 2020

Possibly related: #37719 and #41896

@ianstewart
Copy link
Contributor

ianstewart commented May 11, 2020

I made some notes about the current default state on WP.com.

image

Four pages are created by default …

  • Home
  • About
  • Contact
  • Blog

Home is set as a Homepage in Calypso.

Bug: There is no clear way to unset the Homepage in Calypso …

image

… unless you wanted to make another page a Homepage or a Posts Page.

image

A Posts Page is what a user might call a Blog Page. It’s the status for a Page that tells WordPress to use a particular PHP Theme Template, ignoring the content of a Page, instead “looping” through all the available posts.

We can see the same status in the Customizer although here it is possible to unset the Homepage and revert back to core WordPress defaults.

image

If we un-set the Homepage in the Customizer …

image

Bug: No options are available in Calypso.

@ianstewart
Copy link
Contributor

@johnHackworth @olaolusoga resolving this one won't make the mental model easier to understand but it might be a good quick fix to look at?

@davipontesblog
Copy link
Contributor

Thanks @ianstewart for taking the time to go over the flow here. Ideally, we want to move every action and decision out of the Customizer and into the Pages list here I believe. If that is the goal, we need to ensure users can:

  • Set the site to show either a static page as its homepage or just the blog feed as the homepage;
  • Set a page as homepage in any circumstance;
  • Set a page as "posts" page in any circumstance as well.

These are the decisions and actions you can take in the Customizer today if it helps.

@davemart-in davemart-in added the [Size] M Medium sized issue label Jun 12, 2020
@davemart-in davemart-in added the [Status] Needs Design Add this to PRs that need input from Design label Jun 29, 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

You can also wind up in this state if you have no pages at all.

image

Different from the experience of a default state or theme switch that leaves you with a Blog page.

image

Also, while you can’t delete them from Calypso you can delete the homepage from the editor. But you can’t get to the Blog page from Calypso unless you edit it from the front-end. Which takes you … here?

image

@creativecoder
Copy link
Contributor

This is tough one to solve currently, with so many interrelated parts:

@Addison-Stavlo
Copy link
Contributor

This hasn't moved in a while, idea for a quick fix would be to:

  • Always show the 'homepage status banner'. Im referring to the conditional banner that appears above the page list that says "The homepage is showing your latest posts." and has a link to the front-end of the homepage. To always show, we could show this in the case that posts are set as the homepage as well with a similar but different description.
  • Add a link to to 'Settings -> Reading' within this banner. There Homepage settings are the first option at the top of the page and can be managed there.

It seems like this would be a quick fix that would make this process more visible to users. Since there hasn't been any movement on this, it would be nice to see something helpful - even if just a simple / imperfect solution like adding a quick description and link might be beneficial here. cc @ianstewart - im curious if you have thoughts here?

@Addison-Stavlo
Copy link
Contributor

At this point I think its unclear what needs to be done here in the current state, and is not in our current scope of work. This is less of a bug and more of an unknown feature request. Im removing this from our board since we will not get to it any time soon.

@cuemarie cuemarie added the [Type] Feature Request Feature requests label Mar 29, 2023
@cuemarie cuemarie changed the title Pages: allow setting Homepage from the contextual menu without visiting Customizer Pages: allow setting Homepage from the contextual menu without visiting Customizer or Reading Settings Mar 29, 2023
@cuemarie
Copy link

📌 SCRUBBING NOTES

Still the case that it is not possible to set a page as a static homepage while the homepage is set to the theme default. In that state, the actions for other pages exclude setting as home or posts page:

Markup on 2023-03-29 at 13:09:09

However, once a static homepage is set via the Customer or Settings > Reading, then other pages can be set as home or posts pages via the page list:

Markup on 2023-03-29 at 13:09:43

📌 ACTIONS

  • Landing in 'feature requests' for now

📌 Message to Author

@cuemarie cuemarie added Triaged To be used when issues have been triaged. [Platform] Simple [Platform] Atomic labels Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Pages [Platform] Atomic [Platform] Simple [Size] M Medium sized issue [Status] Needs Design Add this to PRs that need input from Design Triaged To be used when issues have been triaged. [Type] Enhancement [Type] Feature Request Feature requests
Projects
None yet
Development

No branches or pull requests

7 participants