Miscellaneous fixes

[savetheclocktower]

There were lots of broken internal links, since the last incarnation of the manual had fewer pages and more headings.

I also moved the images into the repo and changed the passthrough rule, which should fix #3.

[savetheclocktower]

This one's been updated again with more content for the “adding pulsar to your shell” and “setting up a native module build toolchain” pages.

Some of the stuff in there has been marked with TODOs because we need to fix a couple of things in the code, but even in its pending state I think this would be really useful to show to someone the next time they can't get x-terminal-reloaded to install on Windows.

[confused-Techie]

Overall, this is a fantastic PR!
With the obviously needed fixing of many links being great, I seriously love the lengths you've gone to to reduce any handholding that's needed with the more complex parts of our setup instructions. Ensuring to cover ever edge case, and not just the basic steps of how to get setup, but full options on troubleshooting for the most common issues.

Seriously impressive work. I've added a few comments here and there that I think should be addressed prior to merging, but overall super rad work

[confused-Techie]

While not necessary, I think it'd be a nice thing to note in a much more obvious way that while these are the typical use cases, that there are not at all that could be accomplished.

Maybe something after the list like:

But of course that's not all that a package can do, some package's have found unique problems to solve:
* Word & Character counts
* Showing the time in your editor
* Discord integration to show it as your current activity
* Terminal integration
* Linting your code with select tools

Maybe this list is better off linking to resources, but not sure if it's needed. Just want to make sure that we make it expressly obvious that there's very few limits to what a package can do

[savetheclocktower]

The intent of this section is not to say “a package will do one of these five things,” but rather to say “a package is the method of distribution for each of these five kinds of customization.”

I'm trying (and perhaps failing) to communicate that

• my pulsar-language-svelte package
• my vibrant-ink-redux package
• my calculator-light-ui package
• my symbol-provider-bookmarks package
• and my inline-autocompletion-textmate package

are all distributed the same way even though they do completely different things. It's also unusual for a package to do more than one of these things, even though there's not much enforcement of this in Pulsar.

(For instance: I don't think a single package can function as both a UI theme and a syntax theme, since I think it'll show up in only one of the two theme pickers based on your metadata selection. But either kind of theme package can run code! Its main field in package.json is respected!)

Anyway, I'll add a different section above this about how much freedom you have when authoring packages.

[confused-Techie]

Yeah that sounds awesome to me. I did understand you weren't saying it was a restriction, I just wanted to take the chance to re-iterate the freedom in capabilities.

But if you plan to add it elsewhere, nearby that's fine by me

[confused-Techie]

Suggested change

	* You _must_ have “Desktop development with C++” checked. If it is not selected, select it, then click on the [[Modify]] button at the bottom right corner of the window. It will install new components.
	* You _must_ have “Desktop development with C++” checked. If it is not selected, select it, then click on the [[Modify]] button at the bottom right corner of the window. It will install new components.
	* If your Windows version is something other than Windows 10, ensure you've also checked to install the "Windows 10 SDK"

[savetheclocktower]

You're saying that Windows 11 users will need to install “Windows 10 SDK” just to be able to build a package like x-terminal-reloaded?

[confused-Techie]

From what I recall, yes.

If memory serves there was a support request of someone attempting to setup their toolchain, and they were on Windows 11. But even after installing everything else it wouldn't work, and they had to install the Windows 10 SDK to proceed.

I'll see if I can double check this info, as I'm just relying on my memory, and the fact that I made sure to add that in the docs after that support interaction. But let me see if I can find a source

[confused-Techie]

Alright, @savetheclocktower I've found my original source.

From this interaction, the user was required to install the "Windows 10 SDK" while they were on Windows 11. This looks to be when attempting to install Spiker's terminal package.

But, and apparently I've forgotten about this. But a while back when we bumped the node-gyp version we used, we enabled support of both the Windows 10 SDK and 11. So while my comment was true at one point it no longer is.

So my added docs are now inaccurate. May be a good idea to instead change them to install any SDK version. But if that's not your experience like you said before, it may not be needed and we can omit it entirely. Then if in the future we find some edge cases those can be updated as needed.

[confused-Techie]

As all of my concerns have been addressed, this PR seems like it's good to go.

Super awesome work here, lets get it merged!