Configuration synchronization for nodes utilizing Layout Builder

Moving this to "layout_builder.module".

I believe entity specific overrides for layout are stored within a field on the entity itself, therefore not exportable as config. One of the menu content entity exporters / replicators / syncers should work though.

#2 is correct.

The defaults for entity displays, from Manage Display are exportable.

For individual node settings, from node/[nid]/layout, the overridden layout is stored in a field so would have move the whole node from environment to environment. You would have to find a contrib module solution for that

@MattBrigade, could you give any feedback on this issue? Please let us know if you fixed it and/or understand this is not in the scope of this module.

You'd need to export the entity view display's config (think field formatter settings) alongside using DCD to get the overrides to deploy.
If that doesn't work, there's a bug in DCD.

This is one of things that I like in Page manager that I would love to also have with the Layout builder. The ability of create a structure (page) that is covered by config manager by itself, it would be a major improvement to Layout builder (IMHO).

You could create a content type for each page you need, but that would be sad :)

For now this is a duplicate of #2960739: Create a layout builder variant. There is no plan in place to move Page Manager functionality into core. First we'd need to get it working in Page Manager itself.

I'd shift focus to getting contrib up to par first, and then we can discuss getting it into core.

And to point out: using Page Manager would mean using a non-node entity type. If there is still a desire to force nodes into config via DCD, then file a bug in DCD's queue to figure out why it doesn't work now. The layout builder field is a field type same as any other.

Apparently the layout_builder__layout field is empty when used with Default Content module due to the lack of a normalizer, which would be fixed by #2942975: [PP-1] Expose Layout Builder data to REST and JSON:API

Thanks @sam.mortenson for the tip

@tim.plunkett, I confirm, patch from that issue works fine for me and solved this problem!

Great, thanks for confirming!

I ran into this issue today, completely forgetting that the node layout builder config would be stored in the node/entity level as part of content. #9 suggested creating a content type for each page, however I think another way to do it would be to store the layout config into the Layout Library module as a saved layout, and selecting "Allow content editors to use stored layouts" in the content type Manage Display. Then in the node, select the saved layout in the dropdown.

I will be testing this today and will report back if it works.

Update: It works.

Thanks @chrisck for the layout library suggestion.

Layout Library solves an issue I was pondering for our D7 migration where we are migrating page_manager pages to layout_builder landing pages. Rather than creating each landing page's layout directly, I can instead create a layout_library entity for each landing page with machine name nid_xxxx (where xxxx is the integer nid). This way layouts are in configuration and I just need to map the layout to the node in migration yml by the nid.

I plan to do the same for taxonomy and block layouts.