Regarding the ID discussion started at 44:00, what about cluster setup, there will be multiple distributed stores, are the IDs still guaranteed to be unique?
Brilliant! I am going to start diving into this. The data layer in Orchard Core seems extraordinarily well designed. I'm so glad that you guys managed to integrate GraphQL into your data access layer as well. The power of this architecture can't be understated.
It is highly recommended to post to the Microsoft website for more Chinese developers to see ，because the Chinese network cannot access youtube.com @Microsoft
So, right around the 13 minute mark, they start discussing other platforms and what they do better than Orchard. They get to Wordpress around the 19 minute mark. I just wanted to add that I think the widgets support in Wordpress is much easier to implement - let's say I want to add a gallery widget: I can add a code block in my post content [Gallery:1] and boom, I have a gallery embedded on that page. In Orchard, I have to create a layer, add the widget in the layout section, etc. This makes large, complex websites almost impossible to manage because I lose sight of where my content is and I end up with a layouts page with a crazy amount of layers. Also, mixing public and private content (i.e. show this widget or this block of text if the user is logged in and has a role of 'x') is very difficult to do in Orchard. You have to create a layer for the page that has the shared public/private content, then create a widget for each version of the content (one for public and one for private).
I found OneStop.Layouts on bitbucket. bitbucket.org/onestop/module_onestop_layouts I found a project for OneStop.Slideshow but there's nothing there as of yet (get moving guys!): bitbucket.org/onestop/onestop.slideshow Why aren't these in the Orchard Gallery? There's not a lot of great stuff in the gallery, and it seems there is a lot of great stuff scattered around the web.
