backerman78

@christopheramirian thank you for that information. I’ve read through that and I’m still lost at a high level as to how things come together for plugins in block themes.

I get the theme side of it for full site editing, e.g., setting up the html-esqe template parts made up of blocks for the header or footer, and then full templates that pull in the parts for the main content pages as specified in theme.json.

Aren’t blocks basically self-contained widgets with some UI for entering micro-bits of information and some template for displaying that information? Essentially though, content items are still a specific type of content (page, post, 404, etc.).

But I’m missing how a plugin can integrate with a block theme without there being some kind of configuration (theme.json) or template added to the theme, or being user configured vs being contained within the plugin.

I’m also missing the possible user story with blocks. For example, the user goes in, creates a page and pulls in a staff block and fills it out to make a staff member page. The staff is a page instead of a staff right? Could I query staff for an archive? Could I manage a list of staff separate from the overall content list? Could I set staff specific taxonomies, parent pages, options, etc. all without needing to touch the theme?