Launch Manual V2 Skeleton

[confused-Techie]

While this PR is nowhere near completing the docs, it does have complete sections giving a general layout of the new documentation format.

Essentially here I've followed the ideas from our Discussions and started laying out the docs like I suggested there, additionally I've added some sections for some of the tooling on Pulsar.

The way I envision this be further layed out would be the largest section of Launch Manual then having many subsections. Which in this PR includes

• Pulsar Package Registry Frontend Website
• Authoring Packages

Then each section is able to go into as much detail as needed for that topic. But allows users to easily find what they need to know. The first section here is just about the website itself, and I'd like to see us do this for more of our big ticket items that we use, such as one for PPM, one for Pulsar that could contain just the generic usage of the editor, we could even include ones for some of our bigger or more complicated packages, teletype, and so on.

In this section these would all be user facing documents, not getting into the programming details but just general usage details.

Additionally though we are discussing on Discord how we could include more documentation from specific repos onto the site for developers.

But this is just a start to make sure we like the new layout and see what we can do.

Also to note, this PR purposefully doesn't link to this section of the docs anywhere, as they are so far from complete it'd just be confusing to users to list it publicly at this point. Although this PR would still allow you to navigate by URL to the docs.

[savetheclocktower]

Sorry, I know this is a nitpicky review, but my journalism degree needed exercising.

My main goals were:

• Fix typos.
• Make explanations less conversational and more terse.
• Only use title case in phrases if they describe something with a special meaning, like “Pulsar Package Registry.” Other usages (e.g., “Pulsar User Account”) can be lowercased when they refer to something with a commonly understood meaning.
• When a sentence starts with a subordinate clause, you'll usually want to separate it from the main clause with a comma. The previous sentence illustrates this.

[icecream17]

a few more notes (edit: can't really resolve so hid)

[icecream17]

tbh idk what exactly the update is. patch, minor, or major, or is this about the database somehow?

Edit: Oh this is answered below. This isn't really a review since it comes before the information. Maybe replace with a summary, or move after the info?

[icecream17]

reminds me of this one rust comment. maybe this formulation is simpler:

major - upgrading breaks
minor - downgrading breaks
patch - neither

[confused-Techie]

While that might be a bit simpler, the text taken here iirc is taken directly from the SEMVER docs, and is what we currently use.

But as we do already link to the semver docs maybe we can take the opportunity to make this a bit simpler?

[icecream17]

this formulation isn't exactly the same as semver but it does make things clearer I think...