[wp-trac] [WordPress Trac] #64393: Change how we include Gutenberg in Core

[WordPress Trac]

#64393: Change how we include Gutenberg in Core
------------------------------+---------------------
 Reporter:  youknowriad       |       Owner:  (none)
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+---------------------

Comment (by isabel_brison):

 > Instead of a git submodule, could it just be an empty folder that the
 build process uses to checkout Gutenberg?

 The main difference I see between these two options is that, if we intend
 Core to use PHP files stored in Gutenberg directly, with the empty folder
 strategy it will no longer be possible to run the PHP parts of Core
 without a build step.

 I guess my question is how do we determine which PHP files live in
 Gutenberg and which in Core. For instance, it might make sense for all the
 editor-related files such as block supports to live in Gutenberg, as
 they're closely tied to the JS (and currently they're duplicated across
 both codebases).

 But if we intend to continue using the Gutenberg plugin as an experimental
 development platform there will still be a need to filter, extend or
 override parts of the Core PHP from time to time so new features can be
 tested in the plugin. So from that perspective it's unlikely we'll ever
 fully resolve the problem of porting PHP changes from Gutenberg to Core.

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