[wp-trac] [WordPress Trac] #34923: Introduce basic content authorship in the Customizer

[WordPress Trac]

#34923: Introduce basic content authorship in the Customizer
-------------------------------------+-------------------------------------
 Reporter:  westonruter              |       Owner:  westonruter
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  4.6
Component:  Customize                |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch has-patch    |     Focuses:  ui, accessibility,
  ux-feedback ui-feedback needs-     |  javascript
  testing                            |
-------------------------------------+-------------------------------------

Comment (by celloexpressions):

 @boonebgorges following up on the discussion in devchat, we need some
 guidance here with respect to terms.

 Are there any future plans to introduce a `term_status` field, similar to
 `post_status`? In the customizer, there is currently no mechanism to
 create draft terms that become published when the customizer is saved and
 published. As a result, terms would need to be published immediately,
 which goes against the customizer's principles of previewing everything
 and publishing nothing before the user is ready, but aligns with the way
 terms work everywhere else (for example, when added to post drafts).

 Another possible option might be an internal taxonomy for drafted terms in
 the customizer. Would you foresee that creating issues with the direction
 core is taking taxonomies and terms currently?

 For this ticket, the current question is whether we should wait for future
 core support for draft terms, investigate the viability of an internal
 taxonomy for draft customizer terms, or publish terms immediately when
 they're added in the context of menus, similarly to what happens in the
 post editor and elsewhere. There is currently some disagreement regarding
 the acceptability of immediately publishing terms, but that may be
 necessary based on your perspective on these issues.

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