Contributing Guidelines for the Documentation Repository

[ChampionAsh5357]

This defines the guidelines for contributing to this repo along with the style guide for markdown files. Additionally, this adds a .node-version file to use nvm and nvs with the correct version of Node.

---

Preview URL: https://pr-14.neoforged-docs-previews.pages.dev

[neoforged-pages-deployments]

Deploying with Cloudflare Pages

Name	Result
Last commit:	8dbaf0e2c7a42622fe2e91a3f9da3df5031618ff
Status:	✅ Deploy successful!
Preview URL:	https://f5e91439.neoforged-docs-previews.pages.dev
PR Preview URL:	https://pr-14.neoforged-docs-previews.pages.dev

[ChampionAsh5357]

Reminder to self, should discuss how to document changes between minor and patch versions.

[sciwhiz12]

@ChampionAsh5357, feel free to merge once you're okay with it. I'm not merging mostly because we still have that one unresolved comment, and I'm not sure if you want me to mark it as resolved or keep it unresolved as a note.

[Matyrobbrt]

Maybe an example of using tabs could also be provided?

[sciwhiz12]

Looks good to me, though we should look into the future into making the labels on those tabs be more human-readable.

For example, with the tabs currently in the example, they could be labelled as 20.2.68 and above, 20.2.35 to 20.2.67, and 20.2.0 to 20.2.34, respectively. But this can be done at a later date; maybe even automated to some extent, perhaps as an MDX plugin I think.

[ChampionAsh5357]

Looks good to me, though we should look into the future into making the labels on those tabs be more human-readable.

That would be my assumption. We could also use that plugin to open tabs to the correct location depending on the chosen version as well.

[XFactHD]

Overall looks good to me