Built site for gh-pages

lter · Sep 4, 2024 · 6d8a538 · 6d8a538
1 parent e759cae
commit 6d8a538
Show file tree

Hide file tree

Showing 4 changed files with 36 additions and 29 deletions.
diff --git a/.nojekyll b/.nojekyll
@@ -1 +1 @@
-8a18437d
+6fd2d218
diff --git a/CONTRIBUTING.html b/CONTRIBUTING.html
@@ -232,6 +232,7 @@ <h2 id="toc-title">On this page</h2>
   <ul class="collapse">
   <li><a href="#version-control-github" id="toc-version-control-github" class="nav-link" data-scroll-target="#version-control-github">Version Control &amp; GitHub</a></li>
   <li><a href="#style-guide" id="toc-style-guide" class="nav-link" data-scroll-target="#style-guide">Style Guide</a></li>
+  <li><a href="#file-paths" id="toc-file-paths" class="nav-link" data-scroll-target="#file-paths">File Paths</a></li>
   </ul></li>
   </ul>
 <div class="toc-actions"><ul><li><a href="https://github.com/lter/scicomp/issues/new" class="toc-action"><i class="bi bi-github"></i>Report an issue</a></li></ul></div></nav>
@@ -264,6 +265,12 @@ <h3 class="anchored" data-anchor-id="style-guide">Style Guide</h3>
 </ul></li>
 <li>Use underscores (<code>_</code>) for separating major pieces of information and hyphens (<code>-</code>) in lieu of spaces (e.g., <code>01_find-area.R</code>, <code>harmonize_spp-rich-info.py</code>, etc.)</li>
 </ul>
+</section>
+<section id="file-paths" class="level3">
+<h3 class="anchored" data-anchor-id="file-paths">File Paths</h3>
+<p>When we write code–for ourselves or for working groups–we use <strong>operating system (OS) agnostic file paths</strong>.</p>
+<p>In R, this means using the <code>file.path()</code> function (from base R) to stitch together elements (e.g., <code>file.path("data", "raw_2024.csv")</code>). In Python it means using the <code>join</code> function from the <code>path</code> module of the <code>os</code> library (e.g., <code>os.path.join("data", "raw_2024.csv")</code>).</p>
+<p>If you plan on re-using a file path, assign it to an object/variable (R/Python) to avoid typos/errors when re-using the file path.</p>
 
 
 </section>

diff --git a/search.json b/search.json
@@ -39,14 +39,14 @@
     "href": "CONTRIBUTING.html",
     "title": "LTER Scientific Computing Team",
     "section": "",
-    "text": "This document is meant to focus primarily on our internal processes for contributing. If you’re not a member of this team, we hope you find this document valuable as-is but you should also feel free to make any modifications you feel are necessary if you choose to use our guidelines as a starting place.\n\n\nAs much as possible, use the style of “Conventional Commits” in your commit messages. See here for a nice summary of the highlights of that approach.\nFor minor changes, (1) communicate with the team to avoid merge conflicts and (2) make commits directly to main\nFor major changes, (1) communicate with the team to avoid merge conflicts, (2) open a branch with an intuitive but concise name, and (3) open a pull request when you are confident your edits are largely complete. (4) Request a review from a teammate, (5) make any edits they suggest, (6) merge the PR, and (7) delete the branch.\n\n\n\nFor folder/file names and in code, please follow the following style tips:\n\nUse all lowercase\nRelated files/objects should have a shared file prefix (e.g., wrangle_...)\n\nFor files that have an inherent order, use zero-padded numbers as the prefix (e.g., 01_, 02_, etc.)\n\nUse underscores (_) for separating major pieces of information and hyphens (-) in lieu of spaces (e.g., 01_find-area.R, harmonize_spp-rich-info.py, etc.)"
+    "text": "This document is meant to focus primarily on our internal processes for contributing. If you’re not a member of this team, we hope you find this document valuable as-is but you should also feel free to make any modifications you feel are necessary if you choose to use our guidelines as a starting place.\n\n\nAs much as possible, use the style of “Conventional Commits” in your commit messages. See here for a nice summary of the highlights of that approach.\nFor minor changes, (1) communicate with the team to avoid merge conflicts and (2) make commits directly to main\nFor major changes, (1) communicate with the team to avoid merge conflicts, (2) open a branch with an intuitive but concise name, and (3) open a pull request when you are confident your edits are largely complete. (4) Request a review from a teammate, (5) make any edits they suggest, (6) merge the PR, and (7) delete the branch.\n\n\n\nFor folder/file names and in code, please follow the following style tips:\n\nUse all lowercase\nRelated files/objects should have a shared file prefix (e.g., wrangle_...)\n\nFor files that have an inherent order, use zero-padded numbers as the prefix (e.g., 01_, 02_, etc.)\n\nUse underscores (_) for separating major pieces of information and hyphens (-) in lieu of spaces (e.g., 01_find-area.R, harmonize_spp-rich-info.py, etc.)\n\n\n\n\nWhen we write code–for ourselves or for working groups–we use operating system (OS) agnostic file paths.\nIn R, this means using the file.path() function (from base R) to stitch together elements (e.g., file.path(\"data\", \"raw_2024.csv\")). In Python it means using the join function from the path module of the os library (e.g., os.path.join(\"data\", \"raw_2024.csv\")).\nIf you plan on re-using a file path, assign it to an object/variable (R/Python) to avoid typos/errors when re-using the file path."
   },
   {
     "objectID": "CONTRIBUTING.html#lter-scientific-computing-contributing-guidelines",
     "href": "CONTRIBUTING.html#lter-scientific-computing-contributing-guidelines",
     "title": "LTER Scientific Computing Team",
     "section": "",
-    "text": "This document is meant to focus primarily on our internal processes for contributing. If you’re not a member of this team, we hope you find this document valuable as-is but you should also feel free to make any modifications you feel are necessary if you choose to use our guidelines as a starting place.\n\n\nAs much as possible, use the style of “Conventional Commits” in your commit messages. See here for a nice summary of the highlights of that approach.\nFor minor changes, (1) communicate with the team to avoid merge conflicts and (2) make commits directly to main\nFor major changes, (1) communicate with the team to avoid merge conflicts, (2) open a branch with an intuitive but concise name, and (3) open a pull request when you are confident your edits are largely complete. (4) Request a review from a teammate, (5) make any edits they suggest, (6) merge the PR, and (7) delete the branch.\n\n\n\nFor folder/file names and in code, please follow the following style tips:\n\nUse all lowercase\nRelated files/objects should have a shared file prefix (e.g., wrangle_...)\n\nFor files that have an inherent order, use zero-padded numbers as the prefix (e.g., 01_, 02_, etc.)\n\nUse underscores (_) for separating major pieces of information and hyphens (-) in lieu of spaces (e.g., 01_find-area.R, harmonize_spp-rich-info.py, etc.)"
+    "text": "This document is meant to focus primarily on our internal processes for contributing. If you’re not a member of this team, we hope you find this document valuable as-is but you should also feel free to make any modifications you feel are necessary if you choose to use our guidelines as a starting place.\n\n\nAs much as possible, use the style of “Conventional Commits” in your commit messages. See here for a nice summary of the highlights of that approach.\nFor minor changes, (1) communicate with the team to avoid merge conflicts and (2) make commits directly to main\nFor major changes, (1) communicate with the team to avoid merge conflicts, (2) open a branch with an intuitive but concise name, and (3) open a pull request when you are confident your edits are largely complete. (4) Request a review from a teammate, (5) make any edits they suggest, (6) merge the PR, and (7) delete the branch.\n\n\n\nFor folder/file names and in code, please follow the following style tips:\n\nUse all lowercase\nRelated files/objects should have a shared file prefix (e.g., wrangle_...)\n\nFor files that have an inherent order, use zero-padded numbers as the prefix (e.g., 01_, 02_, etc.)\n\nUse underscores (_) for separating major pieces of information and hyphens (-) in lieu of spaces (e.g., 01_find-area.R, harmonize_spp-rich-info.py, etc.)\n\n\n\n\nWhen we write code–for ourselves or for working groups–we use operating system (OS) agnostic file paths.\nIn R, this means using the file.path() function (from base R) to stitch together elements (e.g., file.path(\"data\", \"raw_2024.csv\")). In Python it means using the join function from the path module of the os library (e.g., os.path.join(\"data\", \"raw_2024.csv\")).\nIf you plan on re-using a file path, assign it to an object/variable (R/Python) to avoid typos/errors when re-using the file path."
   },
   {
     "objectID": "internal_get-data.html",

diff --git 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/scicomp/internal_new-wg-setup.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/index.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/CONTRIBUTING.html</loc>
-    <lastmod>2024-08-30T16:04:53.133Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.022Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/internal_get-data.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/quarto-website_deploy-prep.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/github-connect.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/quarto-website_new-proj.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/googledrive-fxns.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/tutorial_googledrive-pkg.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/tip_packages.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/wg_tools.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/tip_notebook-vs-script.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/tip_names.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/tip_paths.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/internal_deploy-shiny.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/tutorial_quarto-website.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/wg_services.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/wg_facilitation.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/quarto-website_add-content.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/github-create.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/github-website-deploy.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/modules_tutorials/googledrive-auth.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/tutorial_json.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/staff.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/wg_team-coding.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
   <url>
     <loc>https://lter.github.io/scicomp/internal_team-onboard.html</loc>
-    <lastmod>2024-08-30T16:04:53.321Z</lastmod>
+    <lastmod>2024-09-04T16:36:13.210Z</lastmod>
   </url>
 </urlset>