vitepress VS core

There is a discussion related to naming on GitHub: https://github.com/vuejs/vitepress/discussions/548

> I initially gave VitePress a different name because I wanted to be able to explore a different architecture without worrying about backwards compat. After shipping the vuejs.org with VitePress, I believe VitePress is flexible enough to be a full replacement of current VuePress while offering better DX and better performance.

Given that version 1 landed as "VitePress" they probably decided to keep the name.

> ...

> I think we should ship VitePress stable as VuePress 3, but I am open to potential questions and concerns.

> Pros: Less confusion in the long run. There will be just one officially maintained SSG with better DX, better performance, and customization that fully aligns with standard Vite-based Vue apps.

> Cons: Potential confusion in the short run, since there are probably a lot of tutorials / integrations targeting VuePress 1. Still I think with the recent Vue 3 switch, users won't be surprised with a major upgrade for VuePress.

I was inspired by a great series of blog posts and decided to adapt the approach to my needs. In this blog post, I will go over the solution I used in my VitePress site but you can also check a more basic example in this CodePen.

While researching which static site generator we would use, we had a lot of frameworks to pick up from, but only some addressed our needs. While choosing, we needed it to have a good "default" template, out-of-the-box plugins, and be easy to extend its functionalities. From our research, the one that matched most criteria and felt the easiest to start and progress with was Vitepress.

They are using the default theme of VitePress which is a great tool for building content-centric websites such as documentation

Thankfully, an entire ecosystem of frameworks makes docs sites easy to build and services that make static sites easy to deploy. In this post, you'll learn how to build a docs site with VitePress and deploy it to the internet with Render.

I have a few Jekyll blogs including my personal one and I haven't had to touch the Jekyll part for quite a while (it takes a while to compile). I just write in Obsidian and then Github takes over.

I also maintain two VitePress[1] sites. Once I setup it up (I still use Sublime Text), I do the writing on Obsidian.

What I write and see in Obsidian is good enough that I have just done away with looking at how the site looks after I change/add/edit the text. I sometimes do but just to check build and if the sitemaps are generated, etc. -- routine hygiene.

1. https://vitepress.dev

Consider Nuxt instead of Vuepress/Vitepress. If you want the built-in theme in Vitepress, it's great, but if you want to make your own, using Nuxt with the Content plugin is probably better. I found the strong separation between theme and content to be too great, and if I have a docs SSG site using Vitepress and a webapp SSR site using Nuxt, I can't share themes easily anyway.

At least that was my conclusion starting with Vitepress, and ending up with Nuxt 3.

https://nuxt.com/

https://vitepress.dev/ (they haven't decided if they are going to replace Vuepress or not: https://github.com/vuejs/vitepress/discussions/548)

Another option vitepress

Nuxt is an open-source framework for building performant websites and full-stack applications using Vue.js. It provides performance and SEO benefits, and adds full-stack capabilities for Vue apps.

As you can see, it's a simple Single Page Application built with Vue.js where our users can sign up / sign in with a few clicks.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Vue.js is an open source web framework that makes developing web applications easier.

Frameworks and Libraries: There are numerous JavaScript frameworks and libraries, such as React, Angular, and Vue.js, which simplify the development of complex web applications.

Javascript in the browser React - react is a library that gives developers an application programming interface (API) to manipulate the DOM (this is React's ReactDOM package). React uses components and JSX to make building reusable code easier. docs JSX - is a syntax extension for React Javascript code that lets you write HTML-like markup in a javascript file. This makes it easier to write reusable HTML. docs State - a key react concept that guides setting and storage of data between renders. docs Hooks - a key react concept for logic triggered by state change docs Vue - is a framework for building web interfaces. Vue is lightweight and best for small projects prioritizing speed over functionality. doc Angular - web development framework. Angular is best for dynamic more feature rich sites. docs

Vue

Vue 3 Reactivity Source Code

Nonetheless, it offers nearly infinite possibilities. You can code and create anything, from a mobile app with React Native to a desktop application with Electron.js. Furthermore, JavaScript provides excellent frameworks and libraries that can be applied in various approaches, such as React, Three, Vue, Meteor, and Astro.