Goodbye Nextra
Вставка
- Опубліковано 16 тра 2024
- checkout github.com/fuma-nama/fumadocs
My Products
🏗️ WDC StarterKit: wdcstarterkit.com
📖 ProjectPlannerAI: projectplannerai.com
🤖 IconGeneratorAI: icongeneratorai.com
📝 ThumbnailCritique: thumbnailcritique.com
Useful Links
💬 Discord: / discord
🔔 Newsletter: newsletter.webdevcody.com/
📁 GitHub: github.com/webdevcody
📺 Twitch: / webdevcody
🤖 Website: webdevcody.com
🐦 Twitter: / webdevcody
Bro I literally just opened UA-cam to figure out what I'm going to use to make documentation for my project. Are you in my walls? The same thing happened when you did the IaC video a few weeks ago too lol.
Thats such a powerful library, i haven’t checked but it feels similar to how shadcn have its docs. I’ll definitely switch my “custom” docs to this
The search also has a bug in nextra, where when you're scrolled down in the page and start typing in the search, the page scrolls up 😅
have you tried docusaurus? It's pretty popular on large mono repos
Exactly
Hey it's Seb the maintainer of Docusaurus.
Curious to have your thoughts on it ;)
Note unlike other solutions it might not integrate well in the Next.js app (I mean you need a regular HTML nav to navigate from your Next.js landing page to the doc, not a big deal but still something to consider)
@@thisweekinreact I plan on using a sub domain and my code is a mono repo. I am not limited to nextjs.
If you project is a monorepo, maybe you can give a shot to Astro Starlight
You could also try building the docs with contentLayer, that's what I am doing currently. I also tried Nextra and wasn't the happiest with the limitations.
Hi Cody, can you share how you handle breadcrumb elements in next 14 projects? I actually have done it on my hobby project, it feels like very repetitive. I was wondering if you have a better way to do it. Thanks in advance.
The recommended way is to use client components, because layouts aren’t re-rendered. You can use the pathname hook, and put your breadcrumb component inside a layout.
Some folks may use parallel routes, but personally I think it doesn’t worth it, the breadcrumb component won’t dramatically increase your client bundle size, but parallel routes can be quite messy to implement breadcrumbs.
Thank you so much champ, but please answer the questions
1. can I have only the light theme by default?
2. How do we apply our own CSS to fix css bugs?
thoughts on using the starter kit over convex? Will the starter kit replace the need for convex, or will you have a way of integrating convex into this?
Convex is a different path for building your apps. The starter kit is for those who want to use as little third party services as possible and host on a cheap vps.
Hello babe 😊 good job as always ❤
Hi baby 🤗🍼
Thank you
Have a nice day baby
@@alexhichamk6630 ewwww are you stalking me? Cause it’s feeling that way at this point. Please stop.
why do you exactly need dynamically generated docs using app router? most docs frameworks are statically generated at build time, because they are mostly open to public / don't need auth or ssr content
The app router statically builds static output files if you don’t use dynamic data
What vscode icon library are you using?
Lucide
Hmm I know I was pushing nextra earlier (im not using it within a monorepo though), but now Fumadocs seems much more appealing. Thanks for the share!
Sure thing!
Can i know your vscode theme
Have you considered hiring the soot spiders from spirited away to write your documentation ?
I’ll consider that next time
@@WebDevCody 😂❤️
Can we make custom components and import them in the mdx
Yes
@@WebDevCody I had a question, so I want to implement a logic that I would upload a pdf file to my website and based on that pdf file I would make documentation using fumadocs.
@@WebDevCody I figured out how to import components in Mdx file but what do u recommend I should do for the logic described above.
@@WebDevCody so I was thinking I make a backend that receives the pdf file and returns json objects with the data and then I display them in custom components, do u think this is a good idea?
OMG I hate next-js, i once tried it out and the developer feedback was abysmal!!, also the agressive caching was terrible, i don't want vercel to tell me wtf i want!!!!, it left a bad taste in my mouth and i never looked back, i'll checkout remix but MY GOD next-js sucks! 😤
Agree on that, I loved Nuxt.js more than Next.js nowadays
NX also sucks