-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server side pre-rendering for Blazor UI #5519
Comments
Any updates? |
I've been experimenting with Blazor WebAssembly prerendering with ABP and it's so much better experience. Slight disadvantage is that you must somehow pause your users from interacting with the page while app is hydrating in the background. Authenticated prerendering isn't officially supported either. If it's not fully hydrated navigation anchor elements will send requests back to server for more prerendered content defeating purpose and benefits of SPA. I'm convinced simple click blocking transparent CSS overlay with unobtrusive loading bar and working scrollbar does the trick neatly allowing to consume at least some content while waiting for app to fully load. Implementation in ABP should actually be quite simple, changes to existing code are minimal, all we need is extra MVC wrapper like I still need to iron some things out like authentication and state preservation to prevent second-render flicker, but I'm hopeful I'll be able to share a working sample repo soon™. |
any update? |
I've just wrote step-by-step guide on how to achieve basic prerendering with Blazor WebAssembly in ABP 6 (releasing soon). Feel free to give it a try and let me know in comment how it went. ✌ https://community.abp.io/posts/prerendering-blazor-wasm-application-with-abp-6.x-2v8590g3 |
@Xeevis Good work! Did you manage to get further with this? |
Hey, thanks @Znow. I have a prototype site I've made like a year ago that has many of the stuff working I just need to bring it over to latest versions and document it. If you have any particular issues you'd like to see solved as a priority, feel free to open separate issues in my repo. |
I currently don't know if that's possible or how to do. But we should work on that to develop search engine friendly web sites, learn and document best practices on that.
The text was updated successfully, but these errors were encountered: