What about use nextra for Doc builder? #223
Closed
minsoo-web
started this conversation in
Ideas
Replies: 2 comments
-
Thank you @minsoo-web, I thought about migration to other solution because of you. I tested nextra's i18n, hot reloading, nav, footer etc. in my local machine to meet our requirements. When I create docs by docusaurus, my intention was that docs should share markdown file with each packages. But when I testing nextra, we have no reason to migrate our docs to nextra. So I will add Pull Request to migrate our docs to nextra soon. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Now https://suspensive.org use nextra |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I don't think I can use docusaurus well because I don't use it often, but I think it's better to use Nextra because of some of the differences I felt, so I'd like to suggest changing it to Nextra.
The first is hot reload. docusaurus seems to be a static page builder, so I felt like I had to run the dev or build command again every time.
However, nextra is a tool that can create pages using mdx grammar on top of next, so I was able to support hot reload and easily use next's grammar or react's grammar.
The second is that customization is relatively easy.
For example, I think it is much easier to customize because it is not only to use APIs supported by Nextra, such as supporting the right sidebar, customizing footer, scrolling to the top, adding banners, but also to launch the Next app.
The third reason is the utilization of components.
Nextra can declare and import components to draw the screen. I don't know if docusaurus is possible.
I wonder what you think!
@manudeli @okinawaa
Beta Was this translation helpful? Give feedback.
All reactions