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

 @karmatosed Thanks for the feedback!

 > I had a play around with the patch and if I'm right the live preview is
 missing?

 That's correct. This doesn't include anything on the front end. That part
 really needs more discussion, but the live preview will happen
 automatically with this solution.

 > An indication through arrows of reordering over the 'reorder' text. I
 strongly feel that isn't a good text option and an extra click we can do
 without.

 I carried that over from widgets and menus, but removed it in
 [attachment:37974.1.diff], which reduces the amount of code a bit.

 > Padding and lines in the actual panel. It feels super cluttered. Maybe a
 reason we should explore this as a new panel? I'd be keen to see that as
 an experience.

 The Static Front Page area is currently a "section" and the Customizer
 doesn't allow for embedding sections within sections. We could convert it
 to a panel, but that would require reorganizing the current controls a
 bit. I think doing it exactly like the mockup would break backward
 compatibility if anyone is using the current static front page section.

 I did remove the padding in the fly-out panel to more closely mimic the
 mockup. Dividers between controls aren't really used anywhere else, so I
 was wary of introducing those here.

 > Remove word 'page' beside the page as it's that when you are picking. I
 understanding this and other things may be legacy of using menus perhaps?

 The patch is flexible enough to allow themes to register additional post
 types as sections or even reuse the "post collection" control for other
 purposes, which is why I left that label.

 Any feedback to tighten up the UI is much appreciated.

 == Permalinks ==

 [attachment:37974.1.diff] also includes a preliminary attempt to filter
 the permalinks for pages registered as sections to point to the home URL
 with the post ID as a hash. For instance, instead of
 `http://example.com/about/`, the link would be converted to
 `http://example.com/#post-65`. There could be some weirdness with this
 approach, so it'll need some testing.

 An alternative would be to add a new accordion section to the Menus panel
 so that users could explicitly add a link to the anchor on the front page
 instead of relying on the page permalink.

 In either case, if someone tries to access the permalink directly
 (`http://example.com/about/`), it'll redirect to the section on the
 homepage. When switching to a theme without support, the links would
 automatically revert to the permalink format and the redirect would no
 longer happen.

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