I some things here
-
Ok I’m able to change how elements act in default theme → What happens if I export templates to another installation with other settings? Which element leads? Source or import?
-
The version communication. Don’t get me wrong. It’s your baby.
As a user, I feel bad when things suddenly appear out of nowhere that have not been communicated or announced and have a significant impact on the structure.
Now there is also the fact that you have revised the structurearticle, in which there are again new elements that are not on any roadmap nor in the rc to test. I had to revise my comments in my thread now the umpteenth time because any information drops rain in from all sides.
Maybe I’m wrong but isn’t it so that features come in a beta and the RCs are only meant to fix bugs? -
The naming. The name Blocks has multiple meanings and is easily misunderstood. Everything else about this has already been written several times.
-
Ui consistency - We’re able to add prestyled elements like block and container from the elements menu but not the layouts. From the canvas I’m able to create the premade layouts and hitting the + dont’t work as the + menu for elements because it adds instant a block but not a div (maybe here the global option come in the game). Yes I’m able to convert them with right click, we’re also able to talk about. Convert? Ok how? Wait there are two tiny lightgrey icons with a texthover… Why not two simple text options? Convert to div, convert to container.
-
My problems with a consistent didactic workflow I adressed in my thread - no reason to repeat it here.
I would really like to see more transparent communication. I see the cool roadmap and the feature list as a great strength of this product. It creates security and predictability. Quick fixes like this RC version only unsettle parts of the community and especially me.