docs: Waku router under the hood and add guides to website #1311
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
|
tylersayshi
changed the title
hamlim
reviewed
Mar 19, 2025
|
|
||
| When routing around a waku app, you may notice some surprisingly quick navigation speeds. This was my experience while starting development at least. Let's walk through the basic mechanics of the router to get a better shared understanding of how it works and maybe even how to speed things up even further 🚀. | ||
|
|
||
| ## Power of Client-Side Cacheing |
There was a problem hiding this comment.
Small nit: I think the proper spelling is Caching (without the e)
Suggested change
| ## Power of Client-Side Cacheing | |
| ## Power of Client-Side Caching |
|
|
||
| ## Why is This Cool? | ||
|
|
||
| None of this is specific to RSC, nor is it unique to Waku as a framework. However, the ergonomics of `prefetch` paired with the power of the client cacheing static RSC are quite nice features that will not be the default experience everywhere. |
There was a problem hiding this comment.
Suggested change
| None of this is specific to RSC, nor is it unique to Waku as a framework. However, the ergonomics of `prefetch` paired with the power of the client cacheing static RSC are quite nice features that will not be the default experience everywhere. | |
| None of this is specific to RSC, nor is it unique to Waku as a framework. However, the ergonomics of `prefetch` paired with the power of the client caching static RSC are quite nice features that will not be the default experience everywhere. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 :)