prominent note regarding switch to VitePress on VuePress website

[soletan]

Feature request

• Can we have a note on VuePress being out of active development on frontpage of its official website?

I was stumbling over the maintenance mode prompt here on GitHub. I can't remember having seen a similar note on official website. I have been visiting that site quite frequently as a user of VuePress for years. Checking the source repo isn't part of that frequent routine and I guess some more users could utilize the tool and its sources in the same way. Thus, due to the lack of any hint there, users might end up starting new SSG websites based on VuePress hopelessly expecting the 2.x release to come anytime soon.

What problem does this feature solve?

Becoming aware of the fact that VuePress is in maintenance mode for users that don't rely on checking the source repo but the official website for the tool.

What does the proposed API look like?

How should this be implemented in your opinion?

Are you willing to work on this yourself?

[mrienstra]

Came here to say the same thing. Happy to open a PR for this if there is interest.

@ulivz, @bencodezen, @zoolsher

[DaveSanders]

Boy. I just tripped across this while looking for another issue and I'm floored. I've spent the better part of a week working on VP for our app and understanding it, working on extending it, and trying to figure out our various options for search, and then I find out that the product doesn't even have a future.

Feelin' pretty burned right now. This notice should absolutely be front and center on both of the VuePress home pages.

[soletan]

I have to admit, that I'm not sure whether my initial research on this matter still applies or not.

Currently, VitePress is promoted as the little brother to VuePress while VitePress is stating that VuePress has been prepared to work with Vite as well. Sticking with VuePress might be an option. But since there are mixed signals coming from Vuepress (its rather outdated roadmap is stating VuePress to be dropped in favor of VitePress while code maintenance is pretty active) and since I have been adapting our website framework previously based on VuePress to work with VitePress I'll stick to VitePress for now as it comes with a lot less weight on all ends and has clearer future for sure.