Small set of fixes (#147)

* README - Update SnowEx years and url * Book - Projects - Fix typo. * GH Actions - QAQC - Ignore css files --------- Co-authored-by: Jessica Scheick <[email protected]>
uwhackweek · Mar 1, 2024 · 53d170b · 53d170b
1 parent 71922e3
commit 53d170b
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 7 deletions.
diff --git a/.github/workflows/qaqc.yaml b/.github/workflows/qaqc.yaml
@@ -31,7 +31,7 @@ jobs:
       uses: codespell-project/actions-codespell@master
       with:
         check_filenames: true
-        skip: '*.js,qaqc.yml,*.geojson'
+        skip: '*.js,*.css,qaqc.yml,*.geojson'
         ignore_words_file: .codespellignore
         only_warn: 1
 

diff --git a/README.md b/README.md
@@ -15,7 +15,7 @@ We've found that every hackweek benefits from a single-page website to get peopl
 We've used this template for the following events:
 
 * ICESat-2 Hackweek 2022 + 2023: https://icesat-2.hackweek.io
-* SnowEx Hackweek 2021: https://snowex-hackweek.github.io/website/intro.html
+* SnowEx Hackweeks (2021, 2022): https://snowex.hackweek.io
 
 
 ## How to use this template

diff --git a/book/projects/project_roadmap.md b/book/projects/project_roadmap.md
@@ -1,6 +1,6 @@
 # Project Roadmap
 
-Each project will progress through these stages: 
+Each project will progress through these stages:
 
 ```{image} ../img/project-timeline.png
 :alt: flowchart of typical hackweek project timelines
@@ -36,15 +36,15 @@ We facilitate a project team formation session at the end of the first day of th
 ## **Teamwork**
 
 * kick-off meeting focuses on hearing from each team member:
-    * What are your unique learning goals? 
+    * What are your unique learning goals?
     * How do you work best? What level of group interaction works for you?
     * What skills and background are you most excited to share with the team?
     * When are you available to meet?
-* set up team computing infrastructure on Slack and GitHub ([Project Initiallization](project_initialization)) 
+* set up team computing infrastructure on Slack and GitHub ([Project Initialization](project_initialization))
 * project work begins and teams have regular check-ins to chart progress
 * project outputs are recorded in a GitHub repository
 
-## **Presentations** 
+## **Presentations**
 
 * each team has 15 minutes to share what was learned, what challenges arose, what might be worth trying next
 * individual contributions to the group effort are recognized and celebrated
@@ -54,7 +54,7 @@ We facilitate a project team formation session at the end of the first day of th
 * We aspire to keep projects going after the hackweek! This is an optional (ideal) outcome of hackweek project work.
 * Project leads/helpers will transition to longer-term engagement via mentorship role (optional/with support).
 * Additional people join a growing Community of Practice (for example, centered on a community software library).
-* software, research results are packaged and shared/published. 
+* software, research results are packaged and shared/published.