-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
docs: Waku router under the hood and add guides to website #1311
Conversation
This is an idea for a router post. I am happy to reword, restructure or whatever. It was helpful for me to organize my thoughts to look a bit closer at what is loaded when on each route, so I think a post to talk through some of this has some value. Excited to hear what y'all think :)
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging this for now. I think there should be room for improvement for website, like ordering guides, and styling.
Maybe we should mention that Suspense and promises passed from the server can be used in layouts or pages to be able to display content while the rest is still being streamed down from the server. We could link out to the React docs about Suspense for people to learn more about it - https://react.dev/reference/react/Suspense By default, a |
That's no longer the case. #1257 |
This is an idea for a router post. I am happy to reword, restructure or whatever.
It was helpful for me to organize my thoughts to look a bit closer at what is loaded when on each route, so I think a post to talk through some of this has some value.
Excited to hear what y'all think :)