diff --git a/_freeze/internal_contributing/execute-results/html.json b/_freeze/internal_contributing/execute-results/html.json
new file mode 100644
index 0000000..48d5d8e
--- /dev/null
+++ b/_freeze/internal_contributing/execute-results/html.json
@@ -0,0 +1,15 @@
+{
+  "hash": "40758e5eb4ebe614077eba815c943c8e",
+  "result": {
+    "engine": "knitr",
+    "markdown": "---\ntitle: \"SciComp Team Contributing Guidlines\"\nengine: knitr\n---\n\n\nWhile our team is composed of members from different backgrounds, we strive to adhere to a shared set of contributing and style guidelines. This ensures a consistent \"feel\" of our team's products, regardless of which team member took the lead on a particular task.\n\nStandard convention in GitHub is to house such information in a \"CONTRIBUTING.md\" file in the top-level of the relevant repository. We have done that in the repository underpinning this website but you can also quickly jump to that file by clicking [here](https://github.com/lter/scicomp/blob/main/CONTRIBUTING.md).\n\nNote that these are only required for Scientific Computing team members but you may find some of this guidance helpful even if you're not a part of our team.\n",
+    "supporting": [],
+    "filters": [
+      "rmarkdown/pagebreak.lua"
+    ],
+    "includes": {},
+    "engineDependencies": {},
+    "preserve": {},
+    "postProcess": true
+  }
+}
\ No newline at end of file
diff --git a/_quarto.yml b/_quarto.yml
index 6444aeb..f975fc4 100644
--- a/_quarto.yml
+++ b/_quarto.yml
@@ -56,6 +56,8 @@ website:
         menu:
           - text: "People"
             href: staff.qmd
+          - text: "Inernal: Contributing"
+            href: internal_contributing.qmd
           - text: "Internal: Team Onboarding"
             href: internal_team-onboard.qmd
           - text: "Internal: WG Setup"
diff --git a/internal_contributing.qmd b/internal_contributing.qmd
new file mode 100644
index 0000000..c825bbe
--- /dev/null
+++ b/internal_contributing.qmd
@@ -0,0 +1,10 @@
+---
+title: "SciComp Team Contributing Guidlines"
+engine: knitr
+---
+
+While our team is composed of members from different backgrounds, we strive to adhere to a shared set of contributing and style guidelines. This ensures a consistent "feel" of our team's products, regardless of which team member took the lead on a particular task.
+
+Standard convention in GitHub is to house such information in a "CONTRIBUTING.md" file in the top-level of the relevant repository. We have done that in the repository underpinning this website but you can also quickly jump to that file by clicking [here](https://github.com/lter/scicomp/blob/main/CONTRIBUTING.md).
+
+Note that these are only required for Scientific Computing team members but you may find some of this guidance helpful even if you're not a part of our team.