[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:  youknowriad
     Type:  task (blessed)    |      Status:  reopened
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by youknowriad):

 > we keep mentioning “generated files” but aren’t pretty much //all// of
 the
 PHP files //except// for a couple manifest files hand-written and
 maintained?

 > I don’t mind quarantining built files, but the first breakage I noticed
 was the block parser, something absolutely not auto-generated.

 1- Just to make things clear. I'm all for moving as much PHP to Core from
 Gutenberg.
 2- There are some php code and files that is intrinsically related to JS
 code, scripts, modules, routes and styles registration. All of this code
 is "glue" code. It's not really important in Core and it doesn't make
 sense to live on its own. For this kind of php file, I think it doesn't
 make sense to live separate from the JS files... and I don't think make
 sense to write manually either. This is code that is declaratively
 extracted from configuration and conversions. If we resort to manual code
 here, it's just error prone for no real benefit.
 3- I'm also all in favor of unifying Gutenberg and Core repository under
 one repository. It's a decision that I have no say in and would be happy
 to support when/if it happens. My understanding is the main blocker is
 probably trac/Github and processes.

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