[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:  has-ux-feedback needs-patch  |     Focuses:  ui
-----------------------------------------+------------------

Comment (by bradyvercher):

 I talked with @davidakennedy about [comment:119] and [comment:120] and
 those were tested against [attachment:37974.8.diff]. Those particular bugs
 should already be fixed in [attachment:37974.9.diff].

 Replying to [comment:123 @helen]:

 > The usage of the post ID in the fragment URL is a return to ugly
 permalinks - I'm not super excited about using # at all, but whatever it
 is, it should stick to the slug (which should still be editable).

 I can update those to use the slug, but that leaves a few things that need
 to be worked out:

 1. Is there an alternative to using the hash?
 2. Should we update the separator that's used for page hierarchy? For
 example, the page URI for a child would currently be `parent-page/child-
 page`. Do we replace the slash with a dash or underscore instead? The HTML
 4 spec doesn't appear to allow slashes in the `id` attribute, while HTML 5
 does.
 3. If the separator is updated, to what extent should we go to ensure the
 fragments are unique to prevent collisions?
 4. How should themes ensure the anchor is present on the page? A new
 template tag?

 > What are plans for indicating that X pages are the fragments that make
 up Y page on the pages list table?

 I'm all ears if anyone has any ideas on this front.

 > Does this have to hinge on theme support?

 I think it would be a poor experience for users to try to use the feature
 in a theme that doesn't support it. At the very least, themes need to make
 sure the anchor for each section matches the fragment core generates.
 Themes may also need to register a container selector for selective
 refresh to work unless we can inject a temporary container in the
 Customizer preview using `loop_start` and `loop_end`.

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