From 6cf01c669d7f5b03d7b1771a0b1db6ccd2153eec Mon Sep 17 00:00:00 2001
From: Quarto GHA Workflow Runner <quarto-github-actions-publish@example.com>
Date: Wed, 17 Jul 2024 16:36:31 +0000
Subject: [PATCH] Built site for gh-pages

---
 .nojekyll         |  2 +-
 CONTRIBUTING.html | 26 ++++++++++++++++++++++--
 search.json       | 13 +++++++++---
 sitemap.xml       | 52 +++++++++++++++++++++++------------------------
 4 files changed, 61 insertions(+), 32 deletions(-)

diff --git a/.nojekyll b/.nojekyll
index 0664184..e9c1f9e 100644
--- a/.nojekyll
+++ b/.nojekyll
@@ -1 +1 @@
-d546c3c1
\ No newline at end of file
+00a32e53
\ No newline at end of file
diff --git a/CONTRIBUTING.html b/CONTRIBUTING.html
index 2f6210a..5a230ac 100644
--- a/CONTRIBUTING.html
+++ b/CONTRIBUTING.html
@@ -138,6 +138,10 @@ <h2 id="toc-title">On this page</h2>
   <ul>
   <li><a href="#ssecr-contributing-guidelines" id="toc-ssecr-contributing-guidelines" class="nav-link active" data-scroll-target="#ssecr-contributing-guidelines">SSECR Contributing Guidelines</a>
   <ul class="collapse">
+  <li><a href="#editing-course-materials" id="toc-editing-course-materials" class="nav-link" data-scroll-target="#editing-course-materials">Editing Course Materials</a>
+  <ul class="collapse">
+  <li><a href="#avoiding-conflicts" id="toc-avoiding-conflicts" class="nav-link" data-scroll-target="#avoiding-conflicts">Avoiding Conflicts</a></li>
+  </ul></li>
   <li><a href="#accessing-course-materials" id="toc-accessing-course-materials" class="nav-link" data-scroll-target="#accessing-course-materials">Accessing Course Materials</a>
   <ul class="collapse">
   <li><a href="#github" id="toc-github" class="nav-link" data-scroll-target="#github">GitHub</a></li>
@@ -160,6 +164,24 @@ <h2 id="toc-title">On this page</h2>
 
 <section id="ssecr-contributing-guidelines" class="level1">
 <h1>SSECR Contributing Guidelines</h1>
+<section id="editing-course-materials" class="level2">
+<h2 class="anchored" data-anchor-id="editing-course-materials">Editing Course Materials</h2>
+<p>There are three options for editing the course materials:</p>
+<ol type="1">
+<li>Send materials to Nick Lyon for integration into the website</li>
+<li>Work directly in GitHub
+<ul>
+<li>only available if the page(s) you’re editing <u>do not</u> have code chunks</li>
+</ul></li>
+<li>Connect GitHub to your preferred code software (e.g., RStudio, VS Code, etc.) and push local changes to GitHub</li>
+</ol>
+<section id="avoiding-conflicts" class="level3">
+<h3 class="anchored" data-anchor-id="avoiding-conflicts">Avoiding Conflicts</h3>
+<p>If either option 2 or 3 sounds like a good fit for you, we need to be careful we do not cause merge conflicts! Please make a post in the <code>#lter-grad-course</code> channel of the NCEAS Slack organization for <em>both</em> when you start working on the website <em>and</em> when you’re finished.</p>
+<p>If you’re working in a developer environment (i.e., option 3 above), please pull regularly so that you are editing the most up-to-date materials.</p>
+<p>At this point, we are <strong>not</strong> using GitHub branches and/or forks so please just work directly in the ‘main’ branch.</p>
+</section>
+</section>
 <section id="accessing-course-materials" class="level2">
 <h2 class="anchored" data-anchor-id="accessing-course-materials">Accessing Course Materials</h2>
 <section id="github" class="level3">
@@ -173,7 +195,7 @@ <h3 class="anchored" data-anchor-id="shared-drive">Shared Drive</h3>
 </section>
 <section id="communication" class="level3">
 <h3 class="anchored" data-anchor-id="communication">Communication</h3>
-<p>Communicating via email is fine though we also have a channel (<code>#lter-grad-course</code>) in <a href="https://www.nceas.ucsb.edu/">NCEAS</a>’ Slack organization if that is preferable.</p>
+<p>Communicating via email is fine though we also have the <code>#lter-grad-course</code> channel in <a href="https://www.nceas.ucsb.edu/">NCEAS</a>’ Slack organization if that is preferable.</p>
 </section>
 </section>
 <section id="project-management" class="level2">
@@ -181,7 +203,7 @@ <h2 class="anchored" data-anchor-id="project-management">Project Management</h2>
 <ul>
 <li>Individual tasks should be tracked as <a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/quickstart">GitHub Issues</a>
 <ul>
-<li>Be sure that each task is <strong>SMART</strong> (i.e., specific, measurable, achievable, relevant, and time-bound)</li>
+<li>Be sure that each task is <strong>S.M.A.R.T.</strong> (i.e., specific, measurable, achievable, relevant, and time-bound)</li>
 </ul></li>
 <li><strong>Please use the issue template</strong>
 <ul>
diff --git a/search.json b/search.json
index 73fbd52..aeffc5f 100644
--- a/search.json
+++ b/search.json
@@ -532,21 +532,28 @@
     "href": "CONTRIBUTING.html",
     "title": "SSECR Contributing Guidelines",
     "section": "",
-    "text": "We are using a GitHub Team (see here for more information on GitHub Teams) to simplify access protocols to SSECR GitHub materials.\nContact Marty Downs and/or Nick Lyon to be added to the SSECR GitHub Team. This will give you write-level access to (A) the SSECR GitHub repository and (B) the SSECR GitHub Project that we’re using for task management.\n\n\n\nContact Marty Downs and/or Nick Lyon for access to the Google Drive. The Shared Drive is named “LTER-Grad-Course”.\n\n\n\nCommunicating via email is fine though we also have a channel (#lter-grad-course) in NCEAS’ Slack organization if that is preferable.\n\n\n\n\n\nIndividual tasks should be tracked as GitHub Issues\n\nBe sure that each task is SMART (i.e., specific, measurable, achievable, relevant, and time-bound)\n\nPlease use the issue template\n\nWhen you select “New Issue” you will be prompted to use this template automatically\n\nTry to document task progress within the dedicated issue for that task (for posterity)\nStrategic planning (i.e., project management across tasks) should use the SSECR GitHub Project\n\nTask lifecycle can be tracked by dragging an issue’s “card” among columns that correspond to major steps in task completion\n\n\n\n\n\nAs much as possible, use snake case (i.e., all_lowercase_separated_by_underscores). When in doubt, try to maintain consistency with the naming convention and internal structure of other files in the same directory/repository."
+    "text": "There are three options for editing the course materials:\n\nSend materials to Nick Lyon for integration into the website\nWork directly in GitHub\n\nonly available if the page(s) you’re editing do not have code chunks\n\nConnect GitHub to your preferred code software (e.g., RStudio, VS Code, etc.) and push local changes to GitHub\n\n\n\nIf either option 2 or 3 sounds like a good fit for you, we need to be careful we do not cause merge conflicts! Please make a post in the #lter-grad-course channel of the NCEAS Slack organization for both when you start working on the website and when you’re finished.\nIf you’re working in a developer environment (i.e., option 3 above), please pull regularly so that you are editing the most up-to-date materials.\nAt this point, we are not using GitHub branches and/or forks so please just work directly in the ‘main’ branch.\n\n\n\n\n\n\nWe are using a GitHub Team (see here for more information on GitHub Teams) to simplify access protocols to SSECR GitHub materials.\nContact Marty Downs and/or Nick Lyon to be added to the SSECR GitHub Team. This will give you write-level access to (A) the SSECR GitHub repository and (B) the SSECR GitHub Project that we’re using for task management.\n\n\n\nContact Marty Downs and/or Nick Lyon for access to the Google Drive. The Shared Drive is named “LTER-Grad-Course”.\n\n\n\nCommunicating via email is fine though we also have the #lter-grad-course channel in NCEAS’ Slack organization if that is preferable.\n\n\n\n\n\nIndividual tasks should be tracked as GitHub Issues\n\nBe sure that each task is S.M.A.R.T. (i.e., specific, measurable, achievable, relevant, and time-bound)\n\nPlease use the issue template\n\nWhen you select “New Issue” you will be prompted to use this template automatically\n\nTry to document task progress within the dedicated issue for that task (for posterity)\nStrategic planning (i.e., project management across tasks) should use the SSECR GitHub Project\n\nTask lifecycle can be tracked by dragging an issue’s “card” among columns that correspond to major steps in task completion\n\n\n\n\n\nAs much as possible, use snake case (i.e., all_lowercase_separated_by_underscores). When in doubt, try to maintain consistency with the naming convention and internal structure of other files in the same directory/repository."
+  },
+  {
+    "objectID": "CONTRIBUTING.html#editing-course-materials",
+    "href": "CONTRIBUTING.html#editing-course-materials",
+    "title": "SSECR Contributing Guidelines",
+    "section": "",
+    "text": "There are three options for editing the course materials:\n\nSend materials to Nick Lyon for integration into the website\nWork directly in GitHub\n\nonly available if the page(s) you’re editing do not have code chunks\n\nConnect GitHub to your preferred code software (e.g., RStudio, VS Code, etc.) and push local changes to GitHub\n\n\n\nIf either option 2 or 3 sounds like a good fit for you, we need to be careful we do not cause merge conflicts! Please make a post in the #lter-grad-course channel of the NCEAS Slack organization for both when you start working on the website and when you’re finished.\nIf you’re working in a developer environment (i.e., option 3 above), please pull regularly so that you are editing the most up-to-date materials.\nAt this point, we are not using GitHub branches and/or forks so please just work directly in the ‘main’ branch."
   },
   {
     "objectID": "CONTRIBUTING.html#accessing-course-materials",
     "href": "CONTRIBUTING.html#accessing-course-materials",
     "title": "SSECR Contributing Guidelines",
     "section": "",
-    "text": "We are using a GitHub Team (see here for more information on GitHub Teams) to simplify access protocols to SSECR GitHub materials.\nContact Marty Downs and/or Nick Lyon to be added to the SSECR GitHub Team. This will give you write-level access to (A) the SSECR GitHub repository and (B) the SSECR GitHub Project that we’re using for task management.\n\n\n\nContact Marty Downs and/or Nick Lyon for access to the Google Drive. The Shared Drive is named “LTER-Grad-Course”.\n\n\n\nCommunicating via email is fine though we also have a channel (#lter-grad-course) in NCEAS’ Slack organization if that is preferable."
+    "text": "We are using a GitHub Team (see here for more information on GitHub Teams) to simplify access protocols to SSECR GitHub materials.\nContact Marty Downs and/or Nick Lyon to be added to the SSECR GitHub Team. This will give you write-level access to (A) the SSECR GitHub repository and (B) the SSECR GitHub Project that we’re using for task management.\n\n\n\nContact Marty Downs and/or Nick Lyon for access to the Google Drive. The Shared Drive is named “LTER-Grad-Course”.\n\n\n\nCommunicating via email is fine though we also have the #lter-grad-course channel in NCEAS’ Slack organization if that is preferable."
   },
   {
     "objectID": "CONTRIBUTING.html#project-management",
     "href": "CONTRIBUTING.html#project-management",
     "title": "SSECR Contributing Guidelines",
     "section": "",
-    "text": "Individual tasks should be tracked as GitHub Issues\n\nBe sure that each task is SMART (i.e., specific, measurable, achievable, relevant, and time-bound)\n\nPlease use the issue template\n\nWhen you select “New Issue” you will be prompted to use this template automatically\n\nTry to document task progress within the dedicated issue for that task (for posterity)\nStrategic planning (i.e., project management across tasks) should use the SSECR GitHub Project\n\nTask lifecycle can be tracked by dragging an issue’s “card” among columns that correspond to major steps in task completion"
+    "text": "Individual tasks should be tracked as GitHub Issues\n\nBe sure that each task is S.M.A.R.T. (i.e., specific, measurable, achievable, relevant, and time-bound)\n\nPlease use the issue template\n\nWhen you select “New Issue” you will be prompted to use this template automatically\n\nTry to document task progress within the dedicated issue for that task (for posterity)\nStrategic planning (i.e., project management across tasks) should use the SSECR GitHub Project\n\nTask lifecycle can be tracked by dragging an issue’s “card” among columns that correspond to major steps in task completion"
   },
   {
     "objectID": "CONTRIBUTING.html#style-guide",
diff --git a/sitemap.xml b/sitemap.xml
index bb04ce5..38997d5 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,106 +2,106 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://lter.github.io/ssecr/mod_interactivity.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/index.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_data-disc.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_version-control.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/policy_pronouns.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/proj_milestones.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_reproducibility.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/policy_usability.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_reports.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_template.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/policy_attendance.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/CONTRIBUTING.html</loc>
-    <lastmod>2024-07-10T18:08:18.630Z</lastmod>
+    <lastmod>2024-07-17T16:36:02.984Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_project-mgmt.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_credit.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_data-viz.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_spatial.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_next-steps.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_team-sci.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_findings.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_facilitation.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/instructors.html</loc>
-    <lastmod>2024-07-10T18:08:18.670Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.024Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_stats.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/policy_ai.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_wrangle.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/mod_thinking.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/ssecr/policy_conduct.html</loc>
-    <lastmod>2024-07-10T18:08:18.674Z</lastmod>
+    <lastmod>2024-07-17T16:36:03.028Z</lastmod>
   </url>
 </urlset>