[wp-trac] [WordPress Trac] #37974: Add multi-panel feature to pages through add_theme_support

[WordPress Trac]

#37974: Add multi-panel feature to pages through add_theme_support
----------------------------+------------------
 Reporter:  karmatosed      |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  4.7
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  ux-feedback     |     Focuses:  ui
----------------------------+------------------

Comment (by NateWr):

 Replying to [comment:70 karmatosed]:
 > >When they click into Front Page Sections, how are they made aware that
 they need to create child pages to use this feature?
 >
 > They don't need to create child pages to use the feature. I'm confused
 why you think they do? The child pages simply if there are some show in
 the page menu. You don't have that have child pages.

 I was under the impression that the scope had been limited to child pages.
 Even if any page can be added as a section on the home page, the problem
 remains. What happens when a user clicks on Front Page Sections but no
 other pages exist?

 With the existing mockups, it seems that they would be presented with a
 search panel that can not return any results, and no information about
 what kind of results they should expect, or where they can go to get
 sections.

 This is the discoverability issue I'm talking about: when a user goes to
 add sections but there is no available content to add. This interaction
 needs to be mocked up, because it is most likely to be people's first
 engagement with the feature.

 On a second note: was it really decided to allow any page and not just
 child pages? That opens up a whole other can of worms. If someone has an
 existing contact page at `/contact` and then adds that page as a Front
 Page Section, what happens to that old page? Does `/contact` redirect to
 the homepage with a `#contact` anchor? That feels like it could lead to a
 lot of frustration for users if they don't understand what happened to the
 "old" page.

 I think a good portion of the content that is likely to be used with this
 feature (About Us, Contact, Our Team) has real use cases for living on
 both the homepage and a stand-alone page. My understanding was that
 limiting it to child pages was a way to limit this confusion by requiring
 a pre-existing relationship to have been created between the homepage and
 it's sections.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37974#comment:73>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform