Part of

• Simplify and modernize Docsify #2104

Summary

SSR was experimental and incomplete, namely not working with plugins, generally not an ideal way to manage code (duplication of Renderer), and none of us have shown any desire to continue implementing that path.

I have better ideas (discord discussion) on the how to leverage tools like Solid Start,Astro, orQwik.js for SSR and SSG in ways that will be way better than what we had going on.

Note: if we use Astro or Qwik, for example, this opens up the door to allowing people to write not just Vue inside Docsify, but also Solid, React, Svelte, Custom Elements, and more.

So this removes SSR, which we believe is not the ideal way to proceed.

Later, when someone desires and has the time, they can propose a new and complete SSR/SSG implementation that is on a good path, not duplicating a bunch of logic, ideally aligned with modern tech.

Thought leaders from Next.js, Nuxt.js, Solid Start, SvelteKit, and more recently the generic solutions Astro and Qwik, have been ironing out the details of SSR, SSG, CSG for alooooong time; they are masters at it. We should pursue a robust modern solution based on those when we sit down to finally do this.

What kind of change does this PR introduce?

Feature removal: delete SSR.

For any code change,

• Related documentation has been updated if needed
• Related tests have been updated or tests have been added

Does this PR introduce a breaking change? (check one)

• Yes
• No

Breaking change because someone might be using it. This requires a major version bump.

Related issue, if any:

I am planning to finish a few more things in a row here:

#2104.

We can wait for all of those (except perhaps TypeScript) before releasing a major version bump so that we don't release several major version bumps back to back.

Tested in the following browsers:

• Chrome
• Firefox
• Safari
• Edge
• IE