[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):

 I think @celloexpressions raises some good points. I won't discuss them
 further other than to say that I agree.

 Going back to the mockups from @karmatosed. I like these. It's a lot
 easier for me to follow things when it's embedded in the customizer UI I'm
 familiar with.

 They do raise a couple questions about discoverability in the context of a
 fresh install. I think the mockups could be extended to include details
 about what happens when no child pages exist. When they click into Front
 Page Sections, how are they made aware that they need to create child
 pages to use this feature?

 Going back to the use of menus as a basis for the code implementation, I
 believe there's already existing code in place for creating menu "stubs"
 in the customizer. This might be a good approach to this UX problem. I'm
 thinking if no child pages exist, the user could create a stub, give it a
 name, and be told that content can be edited elsewhere.

 That blurs the distinction between content "assembly" and content
 "creation". But I do think some facility will be needed, because having a
 page with no child pages will probably the most common first interaction
 with this feature. That's going to be an important opportunity to
 communicate what it's all about.

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