React, or Vue?

[gaocegege]

/cc @Sepush

We are investigating if we should migrate https://docusaurus.io/ to https://vitepress.vuejs.org/

I think the question we should ask is if we want react, or vue.

We will make an MVP for vitepress to see if it works for us.

[gaocegege]

The benefit of vue.js from my side:

• Community: There may be more vue.js engineers here
• Speed:

[VoVAllen]

I believe live editing is more likely a site generator function instead of builtin functionality of react/vue. Docusaurus seems to support this in v1 facebook/docusaurus#663.

[gaocegege]

docusaurus live updating is a little slower than vitepress, I think.

[hwdef]

react +1

[gaocegege]

Could you please explain more about it? Why do you vote for react 🤔

[hwdef]

It's just some personal reasons.
They are all perfect, no matter which one you choose, it's actually the same.

[Sepush]

VitePress is build on top of Vite

• Faster dev server start
• Faster hot updates
• Faster build (uses Rollup internally)

Lighter page weight

Vue 3 tree-shaking + Rollup code splitting

Does not ship metadata for every page on every request. This decouples page weight from total number of pages. Only the current page's metadata is sent. Client side navigation fetches the new page's component and metadata together.

Others

It is suitable for out-of-the-box documentation use, but the config and theming API may still change between minor releases.

Easy to custom the theme through It's config and theme API.

We could easily build a beautiful doc site via VitePress.
It will looks like:
https://main.vitejs.dev/
https://vitest.dev/

[Sepush]

I will give a demo later this evening.

[Sepush]

Still WIP
https://github.com/Sepush/envd-docs/tree/vitepress
You can git clone this repo and run the following commond to preview

// If you did not use pnpm.It worth a try.

// install pnpm
npm i -g pnpm
// install dependencies
pnpm i
// run to dev
pnpm docs:dev

[Sepush]

It's better than the old version

[gaocegege]

Looking forward to it!

[STRRL]

tldr; I would prefer vitepress rather than docusaurus.

We are investigating if we should migrate docusaurus.io to vitepress.vuejs.org
I think the question we should ask is if we want react, or vue.

I do not think the origin question(docusaurus or vitepress) would leads to the second question(react or vue). Because it seems we are going to build the homepage of envd, it looks like more about a "static site" than an "interactive single-page-application". For building a single page application, I prefer to use React, but for building static site, I prefer to use vitepress at the next time.

I did not use vitepress before, but I prefer to give it a try. We(chao mesh team) are using docusaurus as the tool for generating documentation site, I think docusaurus might be a little hard to configure with both multi-versoning mechanism and i18n. And vitepress and vitepress community have several solution for that:

• Docs versioning mechanism vuejs/vuepress#1018 (comment)
• https://vuepress.vuejs.org/guide/i18n.html#site-level-i18n-config

[gaocegege]

Thanks for your reply!

[VoVAllen]

I investigated a little bit about vue vs react. For the website adoption, the ratio of Vue vs React is 1:1~1:2. Therefore there's no significant gap between them.
For the UI systems, major UI frameworks support both. There're some frameworks only specific framework, but no significant difference in terms of quality or quantity.
For the whole ecosystem, React is bit stronger than Vue, since backed by several company (Meta, vercel, etc.). While vue ecosystem is by a group of individual contributor, for example React SWR vs VueRequest.

Vue is easier for newbies and seems simpler. I personally favor Vue. And @Sepush 's demo looks really nice. One problem is that vitepress seems still in an early stage of development. Is it stable enough now?

[shaonianche]

I believe docusaurus.io or vitepress.vuejs.org can support our work very well.
But for now we have an online version of react, and it doesn't have problems that can't be solved.
I think we should spend some more time on the documentation content ...

[gaocegege]

Yep, I totally agree. The content is more important than the framework.

While Sepush@ can help us migrate to vitepress, it does not break the progress to improve the content, I think.

[shaonianche]

If no one on the current team is good at front-end, then I think it's good to bring in developers and frameworks that are good at it.

[gaocegege]

https://62c7a984e3f8da00081f5046--inspiring-kulfi-9ab7b2.netlify.app/ The vitepress preview looks promising!

Thank @Sepush for the work!

[gaocegege]

Finally, we moved from docusaurus to vitepress. https://envd.tensorchord.ai/

See https://twitter.com/TensorChord/status/1554286590130028544

Thank @Sepush