Recent changes seem to have fixed the problems. I've just realised that Astro doesn't have a schema for sites sourced from WP. Obvious, really

This caused trouble in the Astro sites which source content from WordPress sites like this. The 'Select posts' page is a block page containing selectors for By date — WP Archives block. Works in Astro. By category — WP Categories list. Doesn't work in Astro. By author — ncvp_author_list shortcode because WP doesn't provide a […]

Have four VScode windows up for four sites astro-blog. Native site from content collection called 'blog' astro-local. Local WP fed site. Deployed to Cloudflare directly with % npm run deploy astro-test. First site. Local without content collection astro-wpress. Cloud fed WP site Compare and contrast these files /astro.config.mjs /src/layouts/Layout.astro src/pages/rss.xml.js Issues found astro-blog. Didn't have […]

Categories and tags are the two default WordPress taxonomies used to organise content, with categories serving as broad, mandatory groupings (like topics in a library) and tags providing specific, optional keywords for granular details. Categories are hierarchical (parent/child), while tags are not. In practice individual sites will have their own guidelines for how to use […]

Now it's clear that I don't need full site editing and only need the block editor for the Home and Blog pages, convert all other pages and posts to the classic editor.

I'm surprised this isn't part of WP core. There are a few plugins which address the problem, at least one of which admits to being susceptible to being bypassed by a knowledgeable hacker. It ought to be possible to see how strong a user's password is from the dashboard.