it’s ok but Astro feature set is not properly exploited if you used a 3rd part cms.
first there’s this issue i mentioned earlier where you’ll need a component mapper (from strapi components to astro components) and depending on your needs, you may end up with shit ton of unwanted JavaScript on your page. Include <script> tag only when component used · withastro/roadmap · Discussion #664 · GitHub
second is that there’s no wysiwyg feature (similar to tinacms) which is a bummer i think, but it’s not really related to astro, i’ll give you that…
…but it doesn’t exploit imho one of the strongest feature in astro which is the support of mdx which is tremendously cool when it comes to authoring. you can expose a set of components (as design system, for example) and have a nice markdown editing experience with the power of letting unskilled people add custom blocks. (i believe the new beta markdown blocks will allow the same, but i’m skeptical of the ui)
for a blog i’d rather use plain Astro because the things you can do are much broader (mdx being one of them). if you have separated editors it is not super complicated (as a dev) to setup a dev env for non devs, there are a couple of ways to do it ; one could be to have a docker container run the dev server and mount LiteFS (or something similar) to expose the file system to people willing to edit stuff ; another way could be to mount the repo on an online IDE such as github codespaces, codesandbox or stackblitz.