Merge branch 'main' into security-options

Author: tylergraff

.pre-commit-config.yaml

@@ -36,7 +36,7 @@ repos:
 
   # Misc...
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.6.0
+    rev: v5.0.0
     # ref: https://github.com/pre-commit/pre-commit-hooks#hooks-available
     hooks:
       # Autoformat: Makes sure files end in a newline and only a newline

docs/.eslintrc.json

@@ -42,7 +42,7 @@ Minor updates to the codebase and documentation can be discussed in GitHub issue
 
 <!-- Reusable links -->
 
-[nebari-team]: /docs/community/team-structure
+[nebari-team]: /community/team-structure
 [core-team]: https://github.com/orgs/nebari-dev/teams/core-team
 [consent-decision-making]: https://www.sociocracyforall.org/consent-decision-making/
 [rfd-issue]: https://github.com/nebari-dev/governance/issues/new?assignees=&labels=type%3A+RFD&projects=&template=RFD.md&title=RFD+-+Title

docs/docs/community/code-contributions.mdx renamed to docs/community/code-contributions.mdx

@@ -161,7 +161,7 @@ This command starts a local development server and opens up a browser window.
 Most changes are reflected live without having to restart the server.
 
 :::note
-By default, this will load your site at <http://localhost:3000/>.
+By default, this will load your site at \<http://localhost:3000/\>.
 
 You can specify a different port with `yarn start --port <port-number>`.
 :::
@@ -183,7 +183,7 @@ yarn run serve
 ```
 
 :::note
-By default, this will also load your site at <http://localhost:3000/>.
+By default, this will also load your site at \<http://localhost:3000/\>.
 
 You can specify a different port with `yarn start --port <port-number>`.
 :::

docs/docs/community/decision-making.md renamed to docs/community/decision-making.md

@@ -134,9 +134,7 @@ Our contributing and community guidelines take inspiration from the following pr
 - [Julia Language](https://github.com/JuliaLang/julia/blob/master/CONTRIBUTING.md)
 - [nteract](https://github.com/nteract/nteract/blob/main/CONTRIBUTING.md)
 
-<!-- <DocCardList items={useCurrentSidebarCategory().items} /> -->
-
-<!-- Links -->
+{/*  Links */}
 
 [nebari-issues]: https://github.com/nebari-dev/nebari/issues
 [nebari-prs]: https://github.com/nebari-dev/nebari/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc
@@ -145,7 +143,7 @@ Our contributing and community guidelines take inspiration from the following pr
 [nebari-design]: https://github.com/nebari-dev/nebari-design
 [nebari-governance]: https://github.com/nebari-dev/governance
 
-<!-- Internal links -->
+{/* Internal links  */}
 
 [code-contributions]: community/code-contributions.mdx
 [docs-contributions]: community/doc-contributions.md

docs/docs/community/doc-contributions.md renamed to docs/community/doc-contributions.md

@@ -47,7 +47,7 @@ If an issue is affecting you, start at the top of this list and complete as many
 
 1. Check the [issue tracker][nebari-issues], if there is an open issue for this same problem, add a reaction or more details to the issue
    to indicate that it’s affecting you (tip: make sure to also check the open [pull requests][nebari-prs] for ongoing work).
-2. You should also check the [troubleshooting guide](../troubleshooting.mdx) in these docs to see if your problem is already listed there.
+2. You should also check the [troubleshooting guide][troubleshooting] in these docs to see if your problem is already listed there.
 3. If there is an open issue, and you can add more detail, write a comment describing how the problem is affecting you,
    OR if you can, write up a work-around or improvement for the issue.
 4. If there is not an issue, write the most complete description of what’s happening including reproduction steps.
@@ -66,7 +66,11 @@ The following actions are typically useful:
 - Linking to related issues or discussions while briefly describing how they are related, for instance “See also #xyz for a similar attempt at this” or “See also #xyz where the same thing happened in another cloud provider" provides context and helps the discussion.
 - Summarizing long discussions on issues to help new and existing contributors quickly understand the background, current status, and course of action for the issue.
 
-<!-- links -->
+<!-- Internal links -->
+
+[troubleshooting]: /docs/troubleshooting
+
+<!-- External Links -->
 
 [nebari-issues]: https://github.com/nebari-dev/nebari/issues
 [nebari-labels]: https://github.com/nebari-dev/nebari/labels