[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:55 celloexpressions]:
 > For all of those examples, a lot of the content actually pulls in
 multiple distinct "posts"

 When I first read this ticket, I was hopeful that it would lead to
 something which aims to solve the problems shown in your examples. But
 given how the discussion has played out -- specifically the push-back on
 anything that leans towards "content blocks" -- it looks like that's not
 going to happen.

 I think there are really two proposals being floated in this ticket. I'll
 outline them as I understand them:

 1. Some facility for a page to become an archive of content which is
 attached to that page and doesn't live outside of it. Sure, users can edit
 the child content and move it around, but it's not like posts, events or
 other regularly-updated content. It's static along the current model of
 pages.

 2. Some facility for a page to become a hub of content, with the ability
 to mix-and-match static content that lives on the page with dynamic lists
 of content that live elsewhere.

 The first proposal sounds to me like it's essentially a page which is an
 archive of it's child pages, with some additional UX for re-arranging and
 managing those child pages. The second proposal sounds like we're into
 content blocks.

 I would love to see core tackle the second problem. Although solving the
 first problem might lead to a nifty new feature, I don't believe it will
 do anything to address content-building demands in the wider ecosystem
 which are causing so many problems.

 I understand that may be out-of-scope for this ticket. But I think it
 would be helpful for me, as I try to parse this feature, if the boundaries
 were drawn a little bit more tightly on what problem this is trying to
 solve. Helen has indicated she [doesn't want content
 blocks](https://wordpress.slack.com/archives/core-
 themes/p1474997131000925), but I think a clearer statement on the use-case
 would go a long way towards making decisions about the user flow.

 The putting-pieces-of-content-together-in-one-place bundles too diverse a
 set of use-cases for one feature to solve, unless it really did dig into
 deeper problems like content blocks.

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