Great tutorial. Thank you so much for making this example! 1) There is no step-by-step blog post link in the description. 2) I'd love to see a breakdown of how the Startup configuration allows for the Blazor app to live within the OCC setup, at a low level. Understanding the low level details as far as the middleware pipeline and routing goes, etc. would go a long way in better understanding how this stuff works. 3) With your method, is it possible to also have a server side Blazor application that the client WebAssembly app communicates with, and then have the server-side be an OCC module? I'd prefer to write server-side code that directly loads the dll's it needs to access the OCC API, without having to use HttpRequests from the GraphQL API, and then just let a SignalR connection from the client-side Blazor app update the CMS through that module. 4) I'm curious if there's any degree to which you could combine OCC's form generation system with Blazor, so that you could reference and manipulate OCC-generated content part fields using front-end C# code rather than needing to use JavaScript. Basically, a good way to merge the best aspects of both systems.
Yes, With Orchard Core being in so much flux and not having an official release its difficult to finalize the detailed documentation but I'm working on them. Please be patient.
@@OrchardSkills Then perhaps you should have waited to post this video until you could post the companion blog post. It makes more sense to post the documentation that matches the video you posted - you could define which version of Orchard your posts were written for. I'm sure most people would prefer a blog post that matches the video content and if Orchard changes again the post can either be updated to match or make a note in the post to indicate it is slightly out of date after Orchard changes.
