Skip to content

Commit

Permalink
Built site for gh-pages
Browse files Browse the repository at this point in the history
  • Loading branch information
Quarto GHA Workflow Runner committed Jan 18, 2024
1 parent 76df8e3 commit 8d5a75d
Show file tree
Hide file tree
Showing 4 changed files with 30 additions and 26 deletions.
2 changes: 1 addition & 1 deletion .nojekyll
Original file line number Diff line number Diff line change
@@ -1 +1 @@
a43dcbff
789999fc
10 changes: 7 additions & 3 deletions CONTRIBUTING.html
Original file line number Diff line number Diff line change
Expand Up @@ -286,7 +286,7 @@ <h1>SSECR Contributing Guidelines</h1>
<h2 class="anchored" data-anchor-id="accessing-course-materials">Accessing Course Materials</h2>
<section id="github" class="level3">
<h3 class="anchored" data-anchor-id="github">GitHub</h3>
<p>We are using a GitHub Team (see <a href="https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams">here</a> for more information) to simplify access protocols to SSECR GitHub materials.</p>
<p>We are using a GitHub Team (see <a href="https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams">here</a> for more information on GitHub Teams) to simplify access protocols to SSECR GitHub materials.</p>
<p>Contact Marty Downs and/or Nick Lyon to be added to the SSECR GitHub Team. This will give you <em>write-level access</em> to (A) the <a href="https://github.com/lter/ssecr">SSECR GitHub repository</a> and (B) the <a href="https://github.com/orgs/lter/projects/6">SSECR GitHub Project</a> that we’re using for task management.</p>
</section>
<section id="shared-drive" class="level3">
Expand All @@ -305,8 +305,12 @@ <h2 class="anchored" data-anchor-id="project-management">Project Management</h2>
<ul>
<li>Be sure that each task is <strong>SMART</strong> (i.e., specific, measurable, achievable, relevant, and time-bound)</li>
</ul></li>
<li>Use the issue template and try to document your progress as you work on a given task</li>
<li>Strategic planning (i.e., across all tasks) should use the <a href="https://github.com/orgs/lter/projects/6/views/1">SSECR GitHub Project</a>
<li><strong>Please use the issue template</strong>
<ul>
<li>When you select “New Issue” you will be prompted to use this template automatically</li>
</ul></li>
<li>Try to document task progress within the dedicated issue for that task (for posterity)</li>
<li>Strategic planning (i.e., project management across tasks) should use the <a href="https://github.com/orgs/lter/projects/6/views/1">SSECR GitHub Project</a>
<ul>
<li>Task lifecycle can be tracked by dragging an issue’s “card” among columns that correspond to major steps in task completion</li>
</ul></li>
Expand Down
6 changes: 3 additions & 3 deletions search.json
Original file line number Diff line number Diff line change
Expand Up @@ -263,21 +263,21 @@
"href": "CONTRIBUTING.html",
"title": "SSECR Contributing Guidelines",
"section": "",
"text": "We are using a GitHub Team (see here for more information) 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\nUse the issue template and try to document your progress as you work on a given task\nStrategic planning (i.e., across all 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": "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."
},
{
"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) 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 a channel (#lter-grad-course) 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\nUse the issue template and try to document your progress as you work on a given task\nStrategic planning (i.e., across all 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 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"
},
{
"objectID": "CONTRIBUTING.html#style-guide",
Expand Down
38 changes: 19 additions & 19 deletions sitemap.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2,78 +2,78 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://github.com/lter/ssecr/mod_wrangle.html</loc>
<lastmod>2024-01-18T17:18:16.124Z</lastmod>
<lastmod>2024-01-18T17:24:44.553Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_logic-models.html</loc>
<lastmod>2024-01-18T17:18:15.564Z</lastmod>
<lastmod>2024-01-18T17:24:43.985Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_data-disc.html</loc>
<lastmod>2024-01-18T17:18:14.968Z</lastmod>
<lastmod>2024-01-18T17:24:43.353Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_stats.html</loc>
<lastmod>2024-01-18T17:18:14.400Z</lastmod>
<lastmod>2024-01-18T17:24:42.785Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_facilitation.html</loc>
<lastmod>2024-01-18T17:18:13.844Z</lastmod>
<lastmod>2024-01-18T17:24:42.229Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/topic_spatial.html</loc>
<lastmod>2024-01-18T17:18:13.272Z</lastmod>
<lastmod>2024-01-18T17:24:41.669Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_thinking.html</loc>
<lastmod>2024-01-18T17:18:12.700Z</lastmod>
<lastmod>2024-01-18T17:24:41.097Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_data-viz.html</loc>
<lastmod>2024-01-18T17:18:12.088Z</lastmod>
<lastmod>2024-01-18T17:24:40.473Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_reproducibility.html</loc>
<lastmod>2024-01-18T17:18:11.504Z</lastmod>
<lastmod>2024-01-18T17:24:39.893Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/topic_interactivity.html</loc>
<lastmod>2024-01-18T17:18:10.324Z</lastmod>
<lastmod>2024-01-18T17:24:38.729Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_spatial.html</loc>
<lastmod>2024-01-18T17:18:11.208Z</lastmod>
<lastmod>2024-01-18T17:24:39.609Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_credit.html</loc>
<lastmod>2024-01-18T17:18:11.792Z</lastmod>
<lastmod>2024-01-18T17:24:40.181Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/index.html</loc>
<lastmod>2024-01-18T17:18:12.416Z</lastmod>
<lastmod>2024-01-18T17:24:40.813Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_version-control.html</loc>
<lastmod>2024-01-18T17:18:12.988Z</lastmod>
<lastmod>2024-01-18T17:24:41.385Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_project-mgmt.html</loc>
<lastmod>2024-01-18T17:18:13.556Z</lastmod>
<lastmod>2024-01-18T17:24:41.945Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_reports.html</loc>
<lastmod>2024-01-18T17:18:14.116Z</lastmod>
<lastmod>2024-01-18T17:24:42.501Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_team-sci.html</loc>
<lastmod>2024-01-18T17:18:14.684Z</lastmod>
<lastmod>2024-01-18T17:24:43.069Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/CONTRIBUTING.html</loc>
<lastmod>2024-01-18T17:18:15.292Z</lastmod>
<lastmod>2024-01-18T17:24:43.677Z</lastmod>
</url>
<url>
<loc>https://github.com/lter/ssecr/mod_findings.html</loc>
<lastmod>2024-01-18T17:18:15.848Z</lastmod>
<lastmod>2024-01-18T17:24:44.269Z</lastmod>
</url>
</urlset>

0 comments on commit 8d5a75d

Please sign in to comment.