Hi @alanj - thanks for asking.
The short version is that I am confused about Bricks being a theme and not a plugin and what to do with clients that already have an installation.
Bricks offers some tools for formatting and a different interface to format posts and pages that Gutenberg or the classic editor does not. I do not want to force users into using Bricks or depend on some conversion tool if the client has been … creative …
Bricks builder is not just a template to wrap around. According to Thomas - the recommended route is to - as you do - use gutenberg. I am here referring to the guide on the trial version in the dashboard.
However - The bricks builder also allows me to access pages and posts and edit them in Bricks builder.
This gives me some confusion as to the recommended route. If I could, it would be more consistent to stay in one interface - Bricks builder - where they can also just create pages and posts and so on - in the same interface and forget about Gutenberg, but still allow for compatibility, past and future.
“render a blog post” - refers to the option in the admin bar - Render with Bricks or render with Gutenberg/Wordpress.
The template condition allows me to work in tandem - so the client does not need to think about Bricks. And just continue using the clients gutenberg stuff, with a template that takes the special formatting they have had into consideration. The client comes from another installation with a different theme - and then it has to be transferred to Bricks. this gives some problems because Bricks is a theme - and not a builder. I have not gotten my head around it yet.
As it is now it is not clear to me which way this is heading regarding how the client optimally should edit.
In another post I have asked about how the client should edit content.
Did this help or clarify @alanj ?