thanks to all here, but am going to stay with Classic. i’ve reduced my own site to almost nothing, and the other site i manage has way too much content to re-invent.
i can see the possibilities in Elements, and if i were more serious about web design, i would dive in. here, it’s just a necessary tool i only occasionally use.
have fun ppl!
Thank you - if you ever need to have any site converted, contact us at https://classic-to-elements.com
Happy weaving 
@thominator thanks!
This conversation brings up a lot of useful points on how we can make things easier to understand.
The first-time user experience can be very different, and people coming from Classic might feel a bit confused at the beginning.
Here’s how I usually approach, to answer your question: in every project I add a Starter page with all the basic elements you need to understand how the project is structured. some examples Lander - Cordial - Ascent …
Even for single-page projects, there’s a simplified structure to keep things clear and easy. Linear - Noir
Furthermore, most of the elements on the page are renamed in a logical way to illustrate their function to the user (including the settings of the element itself). The names are sometimes long but very clear, and with the text search it is possible to select only those useful for editing. Always having the page tree in view is essential to understanding the elements
About the guide: Honestly, most of my support work is basically about explaining how Elements works 
In general, users understand things way better when they see the page tree instead of just the preview. I’ll try to improve the instructions, and I’ve noticed that adding screenshots with notes makes everything much clearer.
thanks again
@multithemes Bravo (mostly). You did what @ben didn’t do in Microblog: left the Component name intact, and only added to it (though what’s a “panel”?). @ben changed the name of Collection to Posts in Microblog, which helps understand what the intent of that Component is, but doesn’t help the user at all understand how to replicate that same thing elsewhere (without making the mental link “oh, he renamed it”). Your style helps with both the understanding of what is being done, but also keeps intact the “oh, that’s how he did that” need for understanding Components well.
One comment: I’d make EDIT uppercase everywhere for consistency; leave the thing to be edited (e.g. value) in lowercase. One thing you want to avoid is cognitive dissonance in naming/style; two different names/styles for the same thing makes people stop and think whether something else is intended. I just made a full edit pass in my CMS book looking for those things, and I found enough to guess that this made some bits harder to understand at first glance.
Thom thanks for the advice 
, I’ve also received it privately from other users, and I’d like to take this opportunity to thank everyone.
Since I’m short on space, I made practical choices. The uppercase EDIT only applies to images, allowing you to quickly distinguish them. Then, the sequence of words opens the panel and its options. If you understand the logic then it becomes less confusing, at least that’s the effort I made with the current tools. 
