Redesign TOC navigation

docs/_config.yml

@@ -3,6 +3,7 @@
 
 title: ""
 author: eScience Institute, University of Washington
+copyright: "2024"
 logo: logo.png
 
 # No notebooks in this book
@@ -22,7 +23,7 @@ repository:
 
 # Bibliography
 bibtex_bibfiles:
-  - references.bib
+  - reference/references.bib
 
 sphinx:
   config:

docs/_toc.yml

@@ -3,37 +3,33 @@ root: intro
 parts:
 - caption: Overview
   chapters:
-    - file: overview
-- caption: Tutorial Design
+    - file: overview/overview
+    - file: overview/training-modules
+
+- caption: Organizer Training
   chapters:
-    - file: tutorials/index  
-      sections: 
-        - file: tutorials/tutorial-design
-        - file: tutorials/tutorial-notebooks
-        - file: tutorials/tutorial-presentation
-- caption: Project Design
-  chapters:
-  - file: projects/project-overview
-    sections:
-      - file: projects/project-before
-      - file: projects/project-during
-      - file: projects/project-after
-      - file: projects/project-github
-- caption: Technology
-  chapters:
-    - file: technology/index  
+    - file: training/tutorials/index  
       sections:
-        - file: technology/data-management
-        - file: technology/recognition
-- caption: Strategy and Planning
-  chapters:
-    - file: strategy/index  
-- caption: Learning Culture
-  chapters:
-    - file: culture/index 
+        - file: training/tutorials/tutorial-design
+        - file: training/tutorials/tutorial-notebooks
+        - file: training/tutorials/tutorial-presentation
+    - file: training/projects/index
+      sections:
+        - file: training/projects/project-before
+        - file: training/projects/project-during
+        - file: training/projects/project-after
+        - file: training/projects/project-github
+    - file: training/technology/index  
+      sections:
+        - file: training/technology/data-management
+        - file: training/technology/recognition
+
+    - file: training/strategy/index  
+
+    - file: training/culture/index 
       sections:
-        - file: culture/psychological-safety
+        - file: training/culture/psychological-safety.md
 - caption: Reference
   chapters:
-    - file: bibliography
-    - file: acknowledgements
+    - file: reference/bibliography
+    - file: reference/acknowledgements

docs/intro.md

@@ -1,9 +1,9 @@
-Resources for Organizing a Hackweek
-===================================
+# Resources for Organizing a Hackweek
 
-<font size="4"> Hackweeks are participant-driven events that strive to create welcoming spaces for participants to learn new things, build community and gain hands-on experience with collaboration and team science {cite:p}`Huppenkothen2018`.</font>
 
-<font size="4"> This website provides reference material and training modules to support organizers of earth science themed hackweeks hosted in partnership with The University of Washington's [eScience Institute](https://escience.washington.edu/using-data-science/hackweeks/).</font>
+Hackweeks are participant-driven events that strive to create welcoming spaces for participants to learn new things, build community and gain hands-on experience with collaboration and team science {cite:p}`Huppenkothen2018`
+
+This website provides reference material and training modules to support organizers of earth science themed hackweeks hosted in partnership with The University of Washington's [eScience Institute](https://escience.washington.edu/using-data-science/hackweeks/)
 
 
 ```{image} images/hackweeks.png

docs/overview.md → docs/overview/overview.md

@@ -1,24 +1,31 @@
-# Overview
+# Emergence of the Hackweek
 
 Data permeates nearly every corner of the research landscape. Whether you are a social scientist exploring the impacts of zoning policies on urban demographics, or a physical scientist predicting the effects of climate change on agricultural productivity, you will almost certainly need to develop skills in accessing, processing, visualizing and performing statistical analysis on datasets. 
 
 New technologies have enabled us to have access to ever-increasing volumes of data. At first we usually think, the more data the better! But very quickly we run into challenges. Often a dataset will be too large for us to download and manage it on our local laptop, and we find ourselves trying to subset the data, work with it in the cloud, or find someone else who has a bigger hard drive than yours to download the data. Other times there may be new approaches such as machine learning that would advance our science, but we do not have access to example workflows for applying the tools to our datasets. Even for the most technically savvy of us, keeping up with the dizzying expansion of tools, data formats and technologies is nearly impossible. 
 
 So, how do we learn these tools? If we're already enrolled in a formal education system, we may be lucky enough to find good courses that keep pace with the shifting data science landscape. If not, we typically try to learn from what is on the internet, or we seek out a training workshop. 
 
-## Emergence of the Hackweek
+## A Brief history
 
-Back in 2014, there were very few formal educational pathways to learn data science. So, a group of astronomers designed a workshop combining tutorials and open project work, and called it a "hackweek". They invited members of their own communities to create learning content, and made sure there was ample time for people to work on projects to gain practical experience. Nearly 10 years after the formation of AstroHackweek, this model has been applied across multiple disciplines in over 30 events. Hackweeks have helped us to teach people new skills, create community software and build collaborative networks.
+Back in 2014, there were very few formal educational pathways to learn data science. So, a group of astronomers designed a workshop combining tutorials and open project work, and called it a "hackweek". They invited members of their own communities to create learning content, and made sure there was ample time for people to work on projects to gain practical experience. Importantly, hackweeks are intentionally designed so that *all* participants have an opportunity to:
 
-## Fast Forward 
+* feel like their contributions are valued
+* meet new people outside of their existing circles
+* feel empowered to challenge themselves, make mistakes and have fun
+* learn something new that they came to get from the hackweek
+
+Nearly 10 years after the formation of AstroHackweek, this model has been applied across multiple disciplines in over 30 events. Hackweeks have helped us to teach people new skills, create community software and build collaborative networks.
+
+## Formal Higher Education vs Short-format Training
 
 Today the educational landscape has changed. Many institutions now have their own data science programs, and software is being taught as a component of many discipline-specific offerings. As we continue to reimagine the role of hackweeks, it is useful to explicitly distinguish between these different pathways of learning and community development.
 
 We'll do this by adopting terminology from a recent publication that compares Formal Higher Education with Short-Format Training {cite:p}`williams_optimizing_2023`. Formal Higher Education includes those courses now offered in many universities and colleges. These are typically traditional classroom lectures and may involve some kind of hands-on or lab exercise component. Student performance is evaluated through grading, and everyone follows along a standardized curriculum. Teaching generally requires pedagogical rigor, course evaluation and continuity of curriculum. 
 
 In contrast, Short Format Training refers to workshops, summer schools, boot camps or any other *ad hoc* gatherings aimed at teaching to a specific set of topics. These events are time-bounded and typically of much shorter duration than a university course. The training is often conducted by volunteers who create training modules and may or may not have experience in pedagogical best practices. These events rarely involve any form of evaluation or program improvement, and people hosting and teaching the events usually do not get formally recognized for the work.  We see hackweeks as a special category of Short Format Training, one that is highly adaptive to the emerging needs of a particular community. 
 
-## Benefits of Short-Format Training
+### Benefits of Short-Format Training
 
 If Formal Higher Education is finally catching up with the learning needs of our communities, do we still need Short Format Training and hackweeks? We believe the answer is yes! Here are some reasons why:
 
@@ -27,30 +34,9 @@ If Formal Higher Education is finally catching up with the learning needs of our
 * Short Format Training provides unique opportunities for networking and community building.
 * The absence of learner evaluation requirements in Short Format Trainings frees participants to pursue creative work that might not otherwise occur.
 
-## The Best of Both Worlds?
-
-A critique of Short Format Training is that they lack rigor and that there is limited evidence that they produce positive learning outcomes. We think a big part of this relates to the fact that there have been few studies of their efficacy! However, we recognize that Short Format Training events are often organized with limited funding support and rely largely on the goodwill of a dedicated team of organizers. In such an environment, it is not always realistic to expect the level of consistency and rigor that is possible within a larger Formal Educational structure. 
-
-But, what if we could find ways to injected some of the rigor of Formal Higher Education into our hackweeks, while maintaining our need for flexibility and creativity? In a nutshell, this is the goal of the training and resource materials in this website! 
-
-## Professionalizing Short-Format Training
-
-The modules in this website are designed to prepare organizers of the University of Washington eScience Institute's Hackweek program. We hope to share professional development tools for you to improve your capacity to teach, share ideas, lead project work and advocate for open and reproducible science. We hope the skills acquired here are applicable to other related training you participate in, including those in a Formal Higher Education setting. 
 
-Our first two modules focus on improving our capacity to train hackweek participants to learn new tools for their research. We'll begin by exploring how to choose appropriate *learning content*, which refers to the topics that we choose to present to learners and the depth and breadth of coverage of that content. We will also consider *pedagogy*, which refers to how we teach material, whether in a lecture, discussion- or project-based format, as well as the methods we employ to interact with learners. In our [Tutorial Design](tutorials/index.md) and [Project Design](projects/index.md) modules we will teach you about designing hackweek learning content, and our recommended pedagogical approaches for hackweek particiapants, within the existing framework of our tutorial and project sessions.  
+### Hackweeks: The Best of Both Worlds?
 
-Next we will focus on [Technology](technology/index.md) where we will teach you about the tools we use to create centralized, web-browser accessible learning materials. You will learn to use automated workflows in GitHub to generate consistent and quality controlled Jupyter Notebooks, and we will share resources for hosting sample datasets.
-
-In our [Strategy and Planning](strategy/index.md) module, we will teach you about the tools we use to manage our time and set clear expectations for the various tasks of the organizing team. By structuring the way we work together we can better honor the limited time each of us has to contribute, and ensure that we still meet our broad goals for the event.
-
-Finally, in our module on [Learning Culture](culture/index.md), we will provide opportunities for all of us to practice ways to support a vibrant and healthy learning environment. We will practice skills in building empathy, listening and navigating complex group dynamics. 
-
-## Our Intention for Hackweek Participants
-
-The overall intention of our work here is to support the learning and development of hackweek participants. We believe each participant of our hackweeks should have an opportunity to:
-
-* feel like their contributions are valued
-* meet new people outside of their existing circles
-* feel empowered to challenge themselves, make mistakes and have fun
-* learn something new that they came to get from the hackweek
+A critique of Short Format Training is that they lack rigor and that there is limited evidence that they produce positive learning outcomes. We think a big part of this relates to the fact that there have been few studies of their efficacy! However, we recognize that Short Format Training events are often organized with limited funding support and rely largely on the goodwill of a dedicated team of organizers. In such an environment, it is not always realistic to expect the level of consistency and rigor that is possible within a larger Formal Educational structure. 
 
+**But, what if we could find ways to injected some of the rigor of Formal Higher Education into our hackweeks, while maintaining our need for flexibility and creativity? In a nutshell, this is the goal of the training and resource materials in this website!** 

docs/overview/training-modules.md

@@ -0,0 +1,11 @@
+# Resources for Organizers
+
+The modules in this website are designed to prepare organizers of the University of Washington eScience Institute's Hackweek program. We hope to share professional development tools for you to improve your capacity to teach, share ideas, lead project work and advocate for open and reproducible science. We hope the skills acquired here are applicable to other related training you participate in, including those in a Formal Higher Education setting. 
+
+Our first two modules focus on improving our capacity to train hackweek participants to learn new tools for their research. We'll begin by exploring how to choose appropriate *learning content*, which refers to the topics that we choose to present to learners and the depth and breadth of coverage of that content. We will also consider *pedagogy*, which refers to how we teach material, whether in a lecture, discussion- or project-based format, as well as the methods we employ to interact with learners. In our [Tutorial Design](tutorials/index.md) and [Project Design](projects/index.md) modules we will teach you about designing hackweek learning content, and our recommended pedagogical approaches for hackweek particiapants, within the existing framework of our tutorial and project sessions.  
+
+Next we will focus on [Technology](technology/index.md) where we will teach you about the tools we use to create centralized, web-browser accessible learning materials. You will learn to use automated workflows in GitHub to generate consistent and quality controlled Jupyter Notebooks, and we will share resources for hosting sample datasets.
+
+In our [Strategy and Planning](strategy/index.md) module, we will teach you about the tools we use to manage our time and set clear expectations for the various tasks of the organizing team. By structuring the way we work together we can better honor the limited time each of us has to contribute, and ensure that we still meet our broad goals for the event.
+
+Finally, in our module on [Learning Culture](culture/index.md), we will provide opportunities for all of us to practice ways to support a vibrant and healthy learning environment. We will practice skills in building empathy, listening and navigating complex group dynamics. 

docs/culture/index.md → docs/training/culture/index.md

@@ -1,4 +1,4 @@
-# Introduction
+# Learning Culture
 
 The overall goal of this module is for us to begin building awareness of our own identities and those of others in the context of systemic patterns of power, privilege and marginalization. As our awareness grows we can begin altering our own behaviors to continue fostering psychological safety in group settings. 
 

docs/culture/psychological-safety.md → docs/training/culture/psychological-safety.md

@@ -182,7 +182,7 @@ the exercise might affect how you show up at the hackweek.
 1. Choose 4 different identities that have particular meaning for you when 
 you think about participating in a learning environment, and jot these down 
 in a list.
-1. Take the [image we have provided of a circle](../images/wheel-of-power.jpg).
+1. Take the [image we have provided of a circle](../../images/wheel-of-power.jpg).
 There are four black lines drawn
 on the circle. Write down your identities on these lines, with one word on each
 line. For example, you might write "gender" on one line and "career position" on
@@ -192,7 +192,7 @@ place yourself on the continuum of privilege. The center of the circle
 represents a position of high privilege, and the outer ring represents low
 privilege.
 
-```{image} ../images/wheel-of-power.jpg
+```{image} ../../images/wheel-of-power.jpg
 :alt: Wheel of Power and Privilege
 :class: float-left mr-2 rounded
 :width: 350px