🌐 Update deployment documentation to clarify deployment types

[agoose77]

This PR attempts to clarify the different ways that a MyST site can be deployed (and why you'd pick one over the other).

Closes #927

There's more to cover here, such as deploying a MyST server to Vercel, but I think this is a good start for our JB MVP docs.

[rowanc1]

Can I take a look at this over this week please!

[agoose77]

@rowanc1 are you able to prioritise this over the next two weeks?

[choldgraf]

I think this is a nice improvement on what is there, so I'd be +1 on merging it, though we need to improve these docs as options grow for users to deploy MyST. I think we should link to a Curvenote guide on deploying MyST (or write a short guide in these docs similar to what we have with netlify etc), as well as a similar one for Vercel.

I made a few suggested changes. In particular I suggest we call it MyST Applications rather than Dynamic sites with MyST since the static sites are still plenty dynamic, and I don't want to confuse people into thinking that interactivity is gone just because it's static HTML.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6b94762

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[agoose77]

@choldgraf we're in a space with such a large set of overloaded terms that any attempt to disambiguate things is a good one. Thanks for these changes!