- Removed the Open/Closed project folders from an earlier structure.

- Updated to fix many of the issues with non-relative links.

Author: rbemowski

KB/Guides/Github-desktop.qmd

@@ -92,7 +92,11 @@ In this section, we will walk you through setting up a GitHub repository for a c
 
 
 ## Tracking changes
-Now that you have set up your collaborative Kaggle hackathon repository, it's time to start working on your project and track the changes you make. In this section, we will guide you through the process of adding files to your local repository, viewing and committing changes, and pushing those changes to the remote repository on GitHub. By understanding how to track changes effectively, you and your team can ensure that all contributions are recorded, reviewed, and integrated smoothly into the project.
+Now that you have set up your collaborative Kaggle hackathon repository, it's time to start working on your project 
+and track the changes you make. In this section, we will guide you through the process of adding files to your local
+repository, viewing and committing changes, and pushing those changes to the remote repository on GitHub. By
+understanding how to track changes effectively, you and your team can ensure that all contributions are recorded, 
+reviewed, and integrated smoothly into the project.
 
 1. **Add a blank text file to your local repo**
     1. Right-click repo name in GitHub Desktop → show in explorer (show in Finder and go to the directory on Mac)
@@ -110,7 +114,11 @@ Now that you have set up your collaborative Kaggle hackathon repository, it's ti
 
 
 ## Ignoring .ipynb files 
-As you collaborate on your Kaggle hackathon project, you may encounter challenges with tracking changes in Jupyter notebooks (.ipynb files) due to their complex JSON format. These files can include a lot of metadata that makes version control difficult and cluttered. In this section, we'll show you how to use Jupytext to convert your Jupyter notebooks into a more manageable format and configure your repository to ignore .ipynb files. This approach will help you maintain a cleaner version history and focus on the actual code changes, making collaboration more efficient.
+As you collaborate on your Kaggle hackathon project, you may encounter challenges with tracking changes in Jupyter 
+notebooks (.ipynb files) due to their complex JSON format. These files can include a lot of metadata that makes
+version control difficult and cluttered. In this section, we'll show you how to use Jupytext to convert your Jupyter 
+notebooks into a more manageable format and configure your repository to ignore .ipynb files. This approach will help 
+you maintain a cleaner version history and focus on the actual code changes, making collaboration more efficient.
 
 1. **Add jupyter lab file to repo**
     1. Open anaconda prompt and cd into your local repo folder
@@ -146,7 +154,11 @@ As your team collaborates on the Kaggle hackathon project, it's essential to sta
 
 
 ## Reverting to a previous commit
-During the course of your Kaggle hackathon project, there may be times when you need to revert to a previous version of your code. This could be due to a bug, an unwanted change, or simply the need to return to a stable state. In this section, we'll guide you through the process of reverting to a previous commit using GitHub Desktop. Understanding how to revert to an earlier commit ensures that you can quickly and safely undo changes, helping your team maintain a stable and functional codebase throughout the competition.
+During the course of your Kaggle hackathon project, there may be times when you need to revert to a previous version
+of your code. This could be due to a bug, an unwanted change, or simply the need to return to a stable state. In this
+section, we'll guide you through the process of reverting to a previous commit using GitHub Desktop. Understanding 
+how to revert to an earlier commit ensures that you can quickly and safely undo changes, helping your team maintain 
+a stable and functional codebase throughout the competition.
 
 1. **Find the Commit to Revert To**
     1. Open GitHub Desktop and navigate to the repository you are working on.

KB/Guides/How-to-contribute.qmd

@@ -49,7 +49,10 @@ Ensure the resource is easy to access and use. We want the majority of resources
 Include links to related materials or further readings that can enhance the user’s understanding and provide more in-depth knowledge on the topic. This can include books, articles, other workshops, or case studies. When possible, link to any relevant materials which are already hosted on the Nexus platform.
 
 ### Examples of good posts
-Please see below for a list of resources that meet our platform's standards. You can use these examples in conjunction with the template files provided in the next section to create your post. You can click "Improve this page" near the top right of each resource page to view the corresponding quarto file (.qmd) and code, or find the file in the [GitHub repo](https://github.com/UW-Madison-DataScience/UW-RSE-Nexus).
+Please see below for a list of resources that meet our platform's standards. You can use these examples in conjunction 
+with the template files provided in the next section to create your post. You can click "Improve this page" near the 
+top right of each resource page to view the corresponding quarto file (.qmd) and code, or find the file in the
+[GitHub repo](https://github.com/UW-Madison-DataScience/UW-RSE-Nexus).
 
 #### External content
 
@@ -81,7 +84,7 @@ The high-level steps include :
 
 If you don't know how to use Git / GitHub already, it can be a little intimidating at first. A friendlier 
 alternative could be to [download GitHub desktop](https://desktop.github.com/) and add your post using the instructions provided below. 
-If you'd like to learn more about GitHub Desktop, check out the [Version Control with GitHub Desktop](https://uw-madison-datascience.github.io/ML-X-Nexus/Learn/Guides/Github-desktop.html) guide 
+If you'd like to learn more about GitHub Desktop, check out the [Version Control with GitHub Desktop](/KB/Guides/Github-desktop.qmd) guide 
 on Nexus. If you need additional help (and work in a research lab at UW-Madison), you may also seek help at the 
 Data Science Hub's [office hours ("Coding Meetup")](https://datascience.wisc.edu/hub/#dropin).
 

KB/Presentations/index.qmd

@@ -19,4 +19,4 @@ page-layout: full
 title-block-banner: false
 ---
 Explore past presentations given at UW RSE events. If you have an upcomming presentation or have already given one,
-feel free to [contribute](https://uw-madison-datascience.github.io/UW-RSE-Nexus/KB/Guides/How-to-contribute.html).
+feel free to [contribute](/KB/Guides/How-to-contribute.qmd).

KB/Resources/index.qmd

@@ -19,4 +19,4 @@ page-layout: full
 title-block-banner: false
 ---
 Explore Research Software Engineering resources, on and off campus. If something is missing, please feel free to 
-[contribute](https://uw-madison-datascience.github.io/UW-RSE-Nexus/KB/Guides/How-to-contribute.html).
+[contribute](/KB/Guides/How-to-contribute.qmd).

KB/index.qmd

@@ -24,5 +24,5 @@ toc-location: body
 page-layout: full
 title-block-banner: false
 ---
-Explore previous UW RSE community presentations, projects and other resources. Feel free to [contribute](https://uw-madison-datascience.github.io/UW-RSE-Nexus/KB/Guides/How-to-contribute.html) if you have
+Explore previous UW RSE community presentations, projects and other resources. Feel free to [contribute](/KB/Guides/How-to-contribute.qmd) if you have
 something related to share.

Projects/Closed/index.qmd

@@ -19,5 +19,5 @@ page-layout: full
 title-block-banner: false
 ---
 Explore projects created, managed, or loved by UW RSE community members. If you have a project to share or are looking
-for contributions, please feel free to [contribute](https://uw-madison-datascience.github.io/UW-RSE-Nexus/KB/Guides/How-to-contribute.html) 
+for contributions, please feel free to [contribute](/KB/Guides/How-to-contribute.qmd) 
 a "Projects" page.

Projects/Open/index.qmd

@@ -1,6 +1,6 @@
 # UW RSE Community
 
-![UW RSE Banner](https://uw-madison-datascience.github.io/UW-RSE-Nexus/images/UW-RSE_Logo_Secondary_Transparent.png)
+![UW RSE Banner](/images/UW-RSE_Logo_Secondary_Transparent.png)
 
 Welcome to the GitHup repo for UW RSE Nexus! Nexus is the UW RSE community’s centralized hub for sharing Research
 Software Engineering (RSE) resources. Visit the [UW RSE website](https://hub.datascience.wisc.edu/communities/research-software-engineering-community/) 
@@ -12,7 +12,7 @@ to stay informed on upcoming community events!
 This platform serves as a centralized hub for individuals interested in advancing their knowledge and skills in 
 Research Software Engineering. Whether you're a student, researcher, or industry professional, you'll find a wealth 
 of curated resources tailored to various experience levels and areas of interest.  Visit the 
-[UW RSE Nexus website](https://uw-madison-datascience.github.io/UW-RSE-Nexus/) to begin exploring RSE resources.
+[UW RSE Nexus website](/index.qmd) to begin exploring RSE resources.
 
 ## Features:
 

Projects/index.qmd

@@ -43,5 +43,5 @@ study, you can proudly call yourself a Research Software Engineer.
 ### Share your knowledge on Nexus!  
 This site is powered by contributions from Research Software Engineers like you. If you have a project or other
 Research Software Engineering related resources to share, consider adding it to the UW RSE Nexus. Learn more on our
-[How to contribute](https://uw-madison-datascience.github.io/UW-RSE-Nexus/KB/Guides/How-to-contribute.html) page. 
+[How to contribute](/KB/Guides/How-to-contribute.qmd) page.