Pinging this message thread to see if we can get some further updates and direction from the LCC team. 
I think what we need is something to show us clearly how the new structure is easier, better, simpler, faster because it appears we all see the benefits and logic of the LiveCode Classic structure but can’t really see this with the new Create model. @stam @klaus @thatkeith @Steven
Yeah thats still a question we’ve not had an answer to.
If “card” is to be discarded something else is needed to fill this void.
Looking at XOJO a window or webpage can be constructed with containers/webcontainers which can be swapped out in the window, providing some card/background functionality.
These are as encapsulated as windows with their own events, handlers and props, but creating a navigation system for these is a pain whereas you get that for free with LC cards. I can’t see these being equivalent to LCC containers.
Plus xojo as an app object for base code (similar to a mainstack) as well as a session object for web apps - this is a functional setup but (other than the session object for webapps) not as easy or functional as card/stack/library paradigm.
There are various models that could be implemented to provide multiple layouts for each window, but it appears LCC now implements none of these yet (I don’t count cards because although they exist they are not directly accessible in the IDE), and I’m sure we’re all hoping to see something nice come out of this.
Personally I think cards and stacks could just be renamed to layouts and windows respectively.