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 Aug 28, 2024
1 parent 387db9c commit 59b91ed
Show file tree
Hide file tree
Showing 4 changed files with 29 additions and 28 deletions.
2 changes: 1 addition & 1 deletion .nojekyll
View file
Original file line number Diff line number Diff line change
@@ -1 +1 @@
c97e1260
54e40333
1 change: 1 addition & 0 deletions CONTRIBUTING.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -218,6 +218,7 @@ <h2 class="anchored" data-anchor-id="project-management">Project Management</h2>
</section>
<section id="style-guide" class="level2">
<h2 class="anchored" data-anchor-id="style-guide">Style Guide</h2>
<p>If you are directly contributing to the website, please try to use <a href="https://www.conventionalcommits.org/en/v1.0.0/">Conventional Commits</a> syntax in your commit messages so it is easy for others to identify the purpose and scope of changes made in each commit.</p>
<p>As 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.</p>


Expand Down
4 changes: 2 additions & 2 deletions search.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@
"href": "CONTRIBUTING.html",
"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.\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."
"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\nIf you are directly contributing to the website, please try to use Conventional Commits syntax in your commit messages so it is easy for others to identify the purpose and scope of changes made in each commit.\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",
Expand Down Expand Up @@ -137,7 +137,7 @@
"href": "CONTRIBUTING.html#style-guide",
"title": "SSECR Contributing Guidelines",
"section": "",
"text": "As 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": "If you are directly contributing to the website, please try to use Conventional Commits syntax in your commit messages so it is easy for others to identify the purpose and scope of changes made in each commit.\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": "policy_usability.html",
Expand Down
50 changes: 25 additions & 25 deletions sitemap.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,102 +2,102 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://lter.github.io/ssecr/mod_data-disc.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/index.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/CONTRIBUTING.html</loc>
<lastmod>2024-08-28T16:28:06.311Z</lastmod>
<lastmod>2024-08-28T16:33:39.090Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/policy_usability.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.138Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_spatial.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_stats.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_facilitation.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/proj_milestones.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.138Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_wrangle.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_version-control.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_project-mgmt.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_reports.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/policy_pronouns.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.138Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_findings.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/policy_ai.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.138Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_reproducibility.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/policy_conduct.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.138Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_thinking.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/policy_attendance.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.138Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_team-sci.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/instructors.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_credit.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_data-viz.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_interactivity.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
<url>
<loc>https://lter.github.io/ssecr/mod_next-steps.html</loc>
<lastmod>2024-08-28T16:28:06.355Z</lastmod>
<lastmod>2024-08-28T16:33:39.134Z</lastmod>
</url>
</urlset>

0 comments on commit 59b91ed

Please sign in to comment.