Experimental-theme.json: Move pageTemplates to settings

[carolinan]

What problem does this address?

With the update to theme.json, there are two new sections: settings and styles.
But pageTemplates is also on the root level, -not to be confused with the root block selector:

{
	"settings": {
	},
	"styles": {
	},
	"pageTemplates": {
	}
}

What is your proposed solution?

Because the settings section configures the editor,
it would make sense to move pageTemplates to settings.

[oandregal]

👋 The way I see this, settings and styles configure blocks, not the editor ― hence, why they have core/paragraph, core/group, etc as subkeys.

I think it makes sense to me adding the othe theme metadata as top-level keys. Said this, I'm not sure whether pageTemplates should be its own key or bundled together with other data about templates, etc. Haven't looked deeply into it, so I'll leave others to comment.

[carolinan]

Got it, it made sense to me to have settings in the same place, because I read the docs as if there were only two main sections.

But I don't feel strongly about it and I see that the docs were updated to indicate this 20 hours ago: https://github.com/WordPress/gutenberg/blob/master/docs/designers-developers/developers/themes/theme-json.md

[lukecarbis]

I like the idea of including a third root key called something like theme or meta which contains pageTemplates as a subkey.