Solving or adding up a new hook or api to make [slug] (Leaf Segment) easier and faster to render.

[Gitstar-OC]

Goals

1. Make leaf segments rendering faster
2. Modify the rendering system for leaf segments so that a particular segment can be loaded instead of the whole (bigger) segment.
3. Avoid putting a lot of load on the servers or device in development environment.

Non-Goals

No response

Background

Currently I am using Fumadocs for hosting my educational website which serves a lot of documentation. I have added the leaf routeing for all of the webpages in the website after the /learn/ page and I there lies so many bigger problems in the leaf routing which as mentioned above are also going to be the goals of this.

• It works fine if there are very less number of pages in that leaf section (probably 10 to 20) and saves a ton of work but when it comes to adding more pages (or mdx files) the server or the device takes up a lot of time to make that page possible and compile it.
• If you have visited this website you can see that there are tons of mdx files after the /learn/ page (more than 100) and what that does is takes me more than 5 to 10 minutes to load the leaf segment in development mode and while it gets pre compiled in the build (on vercel) if more users are on the leaf segment it becomes more slower and slower over time.
• The problem with this is that another things on the page also becomes slower (like I have a search thing implemented on my website) and while it looks like only the leaf segment should be slowed as a matter of fact the complete website gets slow.

Various people has raised concerned regarding the performances that I have told (like the search functionality and other things) and I have been looking for a solution since then.

I have asked @fuma-nama the creator of Fumadocs about a fix while the content collections worked for a while, I am still getting errors about that and as I am going to add more docs and sections in my website I think this is going to be a larger problem for my or someone else website which has a lot of thing's under the leaf segment. (You can say like a blog website with lot of blogs as slugs or segments). Just paying more on the servers does not make sense as that does not solve the complete things.

Proposal

I have looked for some solutions to this and have found not many (which I know of or looked in). Maybe as a nextjs community we can test a bit with this things and find up a more better way to reach the goals that I have mentioned. If this helps solve my problems I think problems of more people like me will be solved.