diff --git a/src/archive/2022-2023/README.md b/src/archive/2022-2023/README.md
new file mode 100644
index 0000000..d297cbe
--- /dev/null
+++ b/src/archive/2022-2023/README.md
@@ -0,0 +1,2 @@
+# 2022-2023 Docs
+Docs created within the 2022-2023 academic year.
\ No newline at end of file
diff --git a/src/archive/2022-2023/demos/1/README.md b/src/archive/2022-2023/demos/1/README.md
new file mode 100644
index 0000000..24f58b7
--- /dev/null
+++ b/src/archive/2022-2023/demos/1/README.md
@@ -0,0 +1,141 @@
+# Demo #1, February 2nd
+
+## Spirit
+
+1. Get to know the technical side of your project
+   a little bit more
+   and the things you've build so far,
+   or plan on building.
+2. Discovering how we can help you.
+3. Help you get out of the way the challenges you see.
+4. Monitoring progress is not a goal,
+   don't feel pressured,
+   this Demo shouldn't require much preparation,
+   and instead is more of a sincere conversation.
+
+## Agenda
+
+We'll go to the table where you are with your team
+and talk with you there.
+
+Driven by the project manager:
+
+1. Mention your project's name,
+   the name of its members,
+   and a short phrase about what your project is about,
+   and what problem it solves for its consumers.
+
+2. Walk us through your vision:
+
+   - How do you want your project to look like 3 months for now?
+
+   - Are there any challenges you are facing or may face?
+
+   - What's your number 1 priority as a team right now?
+   - What's your number 1 priority as a project manager?
+
+3. Technical overview:
+
+   - What's your chosen tech stack?
+
+   > Note: "Source Code" below means code, diagrams, designs, plots, anything.
+
+   - Walk us through how a Developer
+     would clone/access your Source Code
+     and get started contributing.
+
+   - Walk us through your Source Code.
+
+   - What would be the top 1 thing that if implemented
+     would make your team contributing experience happier?
+
+4. Any closing thoughts?
+<!--
+
+The spirit of this demo is to:
+
+1. Allow each project to show the things they have worked on
+   and receive feedback from other members of the club.
+
+   We'll be your beta testers once there is something to test!
+   And this initial feedback and market validation
+   will hopefully help you shape a better project.
+
+1. See the approaches that other teams took when building their project.
+
+   So for instance, if your team is a web app,
+   you'll be able to see firsthand how other teams work
+   on a mobile app, robotics project, browser extension, etc,
+   while also allowing them to learn about how you are building a web app.
+
+1. Hear each team's challenges and experiences
+   while working in their specific domain,
+   using their chosen tech stack, and so on,
+   allowing you to learn from other people's experiences.
+
+## Guidelines
+
+To make the most out of the demos,
+please follow the following guidelines:
+
+1. Mention your project's name,
+   the name of its members,
+   and a short phrase about what your project is about,
+   and what problem it solves for its consumers.
+
+   There is no need to be super-specific,
+   but it’s useful to think
+   that this demo can be the first point of contact
+   for a new user with your project.
+   we want you to be able to perfect this initial pitch.
+
+   Please keep it simple.
+   For example: “Hi there! This is Kevin from the TodoApp team.
+   TodoApp is a mobile application that helps people
+   keep track of the tasks they have to do
+   in a friendly way so that they never forget them”.
+
+1. For each of the things you have worked on so far
+   but without including what you demoed in the previous month:
+
+   1. Start by mentioning the purpose of what you have worked on so far
+      and how it fits in the big picture.
+
+      For example:
+      “In this cycle we wanted our users to be able
+      to customize the theme in the application.”
+
+   1. Mention the why.
+
+      For example: “Many of our users spend a lot of time using screens
+      and we wanted to help them reduce eye strain by using a Dark theme.
+      If you are one of those users who prefer a light theme,
+      no worries,
+      we have you covered:
+      the theme choice is completely up to you.”.
+
+   1. Walk the users through the tangible changes.
+
+      For example: “To configure the theme, please click on your profile, scroll down to the end of the page, and check the theme of your preference.”
+
+      Make sure you walk a user through your project as you are talking,
+      you can show a live version of the functionality of your project,
+      or you can show recordings or images.
+
+   1. Repeat for each of the other things you worked on.
+
+1. Mention what's in your [RoadMap](../roadmap/) for the next months.
+   This is an awesome opportunity to get them excited for what's to come
+   and also to get some early feedback/market validation
+   even before starting with the implementation.
+
+1. Make a close,
+   you can remember users how to start using your project and
+   where to provide feedback (GitHub issues for example),
+   and maybe encourage them to click
+   on the "star" button of your project repository.
+   -->
+
+May your projects be successful!
+
+![Used By Many People](../used-by.png)
diff --git a/src/archive/2022-2023/demos/2/README.md b/src/archive/2022-2023/demos/2/README.md
new file mode 100644
index 0000000..3e38ead
--- /dev/null
+++ b/src/archive/2022-2023/demos/2/README.md
@@ -0,0 +1,50 @@
+# Demo #2, March 16th
+
+## Spirit
+
+1. Get to know the technical side of your project
+   a little bit more
+   and the things you've build so far,
+   or plan on building.
+2. Discovering how we can help you.
+3. Help you get out of the way the challenges you see.
+4. Monitoring progress is not a goal,
+   don't feel pressured,
+   this Demo shouldn't require much preparation,
+   and instead is more of a sincere conversation.
+
+## Agenda
+
+We'll go to the table where you are with your team
+and talk with you there.
+
+Driven by the project manager:
+
+1. Elevator Pitch (30 - 60 seconds)
+
+   > Goal: keep it short, sweet, and memoriable.
+
+   - Introduce your project's name and members.
+   - Discuss the problem you are attempting to solve
+   - What is your solution?
+   - How does your solution specifically addresses the problem.
+
+2. Progress and Challenges faced since Demo #1:
+
+   - Recap: What's your chosen tech stack (code, diagrams, designs, plots, ect)?
+   - Overall, what has been worked on since Demo #1?
+   - What are 3 main sucesses the team is proud of since Demo #1?
+   - What are some major challenges that were encountered? How did you overcome them?
+
+3. Roadmap for the Final Showcase:
+
+   - What do you hope to achieve by the **Final Showcase on April 29th, 2023**?
+   - Where do you sit on your timeline for progression for the above goal?
+   - Are there any challenges you are currently facing or may face?
+   - What resource(s) would be useful to help the team achieve the goal? For example, aid in understanding how to deploy in AWS or the app store from creditable and effective online resources or an industry professional.
+
+4. Any closing thoughts?
+
+May your projects be successful!
+
+![Used By Many People](../used-by.png)
diff --git a/src/archive/2022-2023/demos/3/README.md b/src/archive/2022-2023/demos/3/README.md
new file mode 100644
index 0000000..64bbe1f
--- /dev/null
+++ b/src/archive/2022-2023/demos/3/README.md
@@ -0,0 +1,61 @@
+# Demo #3, April 6th
+
+## Spirit
+
+1. Do a final showcase simulation.
+1. Show the world what you've built.
+1. See what other teams have built.
+1. No matter what, enjoy the process.
+
+   The amount of hard work, dedication,
+   and teamwork required to bring an idea to life is immense,
+   and you should all feel incredibly proud
+   of what you have accomplished in the last two seasons.
+   You have overcome countless obstacles and challenges,
+   honed your skills, and become a better version of yourself.
+   Now, as you stand at the finish line
+   and look back on what you have achieved,
+   take a moment to appreciate how far you have come
+   and how much you have grown.
+   Your project is a testament to your passion, creativity, and perseverance,
+   and it serves as a reminder that with the right mindset and determination,
+   anything is possible.
+
+## Agenda
+
+The content is up to you!
+The way you deliver your presentation matters,
+so feel free to drop here your signature style.
+
+Just remember that in the final showcase
+(and therefore in this demo),
+you'll have:
+
+- Maximum 15 minutes for your presentation.
+- Maximum 3 minutes for questions and answers.
+- Most of the audience will be completely new to your project.
+- Teams will present in the following order:
+
+  1. Bandist.
+  1. CyberHire.
+  1. EasyMeal.
+  1. LifeLine.
+  1. AiRM.
+  1. TechstArcade.
+- The judges will score based on
+  [this rubric](https://docs.google.com/document/d/1scLIovkpHQizCwvwH1ql02NYGKR--tHjXpN2FT3Lsyw/edit?usp=sharing),
+  so if you want to win some prizes you may want to optimize for that.
+- Please prepare your responses for the following retrospective questions:
+   - What was the most challenging aspect of the project and how did you overcome it?
+   - Looking back, what would you have done differently in terms of planning or execution?
+   - How did each team member contribute to the project, and what strengths did they bring to the team?
+   - What did you learn from working on this project that you can apply to future projects?
+   - In what ways did the project meet or exceed your initial expectations, and why?
+   - Did you feel that the project had a meaningful impact, either for your team or for others?
+   - What is your plan for the next 3 weeks leading up to the final showcase?
+
+Lastly, just remember to look back on what you have achieved,
+and take a moment to appreciate how far you have come
+and how much you have grown.
+
+We all feel very proud of you and believe in you.
diff --git a/src/archive/2022-2023/demos/README.md b/src/archive/2022-2023/demos/README.md
new file mode 100644
index 0000000..97ccfb7
--- /dev/null
+++ b/src/archive/2022-2023/demos/README.md
@@ -0,0 +1,15 @@
+# Demos
+
+At Tech Start UCalgary
+all projects are showcased to the world
+at the end of each academic year.
+In this event, people from different industries and backgrounds
+come and give us feedback on the projects,
+while also allowing you as a professional and us as a club
+to connect and network with different companies.
+
+This year's showcase is scheduled for **April 29th, 2023**.
+To prepare for the showcase
+we want each team to demo their project
+on the last dev night of every month until the showcase.
+Namely, February 2nd, March 16th, and April 6th, all in 2023.
diff --git a/src/archive/2022-2023/demos/used-by.png b/src/archive/2022-2023/demos/used-by.png
new file mode 100644
index 0000000..43ee814
Binary files /dev/null and b/src/archive/2022-2023/demos/used-by.png differ
diff --git a/src/archive/README.md b/src/archive/README.md
new file mode 100644
index 0000000..d2bb9a5
--- /dev/null
+++ b/src/archive/README.md
@@ -0,0 +1,4 @@
+# Archive
+Docs from previous years that we keep around for the nostalgia.
+Information in here may or may not be up to date, so ask on the 
+Discord if you have any questions!
diff --git a/src/projects/demos/1/README.md b/src/projects/demos/1/README.md
index f211aa9..03f33e5 100644
--- a/src/projects/demos/1/README.md
+++ b/src/projects/demos/1/README.md
@@ -1,141 +1,4 @@
-# Demo #1, February 2nd
+# Demo & Pitch Night 1
+## 30 November 2023
 
-## Spirit
-
-1. Get to know the technical side of your project
-   a little bit more
-   and the things you've build so far,
-   or plan on building.
-2. Discovering how we can help you.
-3. Help you get out of the way the challenges you see.
-4. Monitoring progress is not a goal,
-   don't feel pressured,
-   this Demo shouldn't require much preparation,
-   and instead is more of a sincere conversation.
-
-## Agenda
-
-We'll go to the table where you are with your team
-and talk with you there.
-
-Driven by the project manager:
-
-1. Mention your project's name,
-   the name of its members,
-   and a short phrase about what your project is about,
-   and what problem it solves for its consumers.
-
-2. Walk us through your vision:
-
-   - How do you want your project to look like 3 months for now?
-
-   - Are there any challenges you are facing or may face?
-
-   - What's your number 1 priority as a team right now?
-   - What's your number 1 priority as a project manager?
-
-3. Technical overview:
-
-   - What's your chosen tech stack?
-
-   > Note: "Source Code" below means code, diagrams, designs, plots, anything.
-
-   - Walk us through how a Developer
-     would clone/access your Source Code
-     and get started contributing.
-
-   - Walk us through your Source Code.
-
-   - What would be the top 1 thing that if implemented
-     would make your team contributing experience happier?
-
-4. Any closing thoughts?
-<!--
-
-The spirit of this demo is to:
-
-1. Allow each project to show the things they have worked on
-   and receive feedback from other members of the club.
-
-   We'll be your beta testers once there is something to test!
-   And this initial feedback and market validation
-   will hopefully help you shape a better project.
-
-1. See the approaches that other teams took when building their project.
-
-   So for instance, if your team is a web app,
-   you'll be able to see firsthand how other teams work
-   on a mobile app, robotics project, browser extension, etc,
-   while also allowing them to learn about how you are building a web app.
-
-1. Hear each team's challenges and experiences
-   while working in their specific domain,
-   using their chosen tech stack, and so on,
-   allowing you to learn from other people's experiences.
-
-## Guidelines
-
-To make the most out of the demos,
-please follow the following guidelines:
-
-1. Mention your project's name,
-   the name of its members,
-   and a short phrase about what your project is about,
-   and what problem it solves for its consumers.
-
-   There is no need to be super-specific,
-   but it’s useful to think
-   that this demo can be the first point of contact
-   for a new user with your project.
-   we want you to be able to perfect this initial pitch.
-
-   Please keep it simple.
-   For example: “Hi there! This is Kevin from the TodoApp team.
-   TodoApp is a mobile application that helps people
-   keep track of the tasks they have to do
-   in a friendly way so that they never forget them”.
-
-1. For each of the things you have worked on so far
-   but without including what you demoed in the previous month:
-
-   1. Start by mentioning the purpose of what you have worked on so far
-      and how it fits in the big picture.
-
-      For example:
-      “In this cycle we wanted our users to be able
-      to customize the theme in the application.”
-
-   1. Mention the why.
-
-      For example: “Many of our users spend a lot of time using screens
-      and we wanted to help them reduce eye strain by using a Dark theme.
-      If you are one of those users who prefer a light theme,
-      no worries,
-      we have you covered:
-      the theme choice is completely up to you.”.
-
-   1. Walk the users through the tangible changes.
-
-      For example: “To configure the theme, please click on your profile, scroll down to the end of the page, and check the theme of your preference.”
-
-      Make sure you walk a user through your project as you are talking,
-      you can show a live version of the functionality of your project,
-      or you can show recordings or images.
-
-   1. Repeat for each of the other things you worked on.
-
-1. Mention what's in your [RoadMap](../roadmap/) for the next months.
-   This is an awesome opportunity to get them excited for what's to come
-   and also to get some early feedback/market validation
-   even before starting with the implementation.
-
-1. Make a close,
-   you can remember users how to start using your project and
-   where to provide feedback (GitHub issues for example),
-   and maybe encourage them to click
-   on the "star" button of your project repository.
-   -->
-
-May your projects be successful!
-
-![Used By Many People](../used-by.png)
+Coming soon...
\ No newline at end of file
diff --git a/src/projects/demos/2/README.md b/src/projects/demos/2/README.md
index 243f737..55aa053 100644
--- a/src/projects/demos/2/README.md
+++ b/src/projects/demos/2/README.md
@@ -1,50 +1,4 @@
-# Demo #2, March 16th
+# Demo & Pitch Night 2
+## Early-Mid February 2024
 
-## Spirit
-
-1. Get to know the technical side of your project
-   a little bit more
-   and the things you've build so far,
-   or plan on building.
-2. Discovering how we can help you.
-3. Help you get out of the way the challenges you see.
-4. Monitoring progress is not a goal,
-   don't feel pressured,
-   this Demo shouldn't require much preparation,
-   and instead is more of a sincere conversation.
-
-## Agenda
-
-We'll go to the table where you are with your team
-and talk with you there.
-
-Driven by the project manager:
-
-1. Elevator Pitch (30 - 60 seconds)
-
-   > Goal: keep it short, sweet, and memoriable.
-
-   - Introduce your project's name and members.
-   - Discuss the problem you are attempting to solve
-   - What is your solution?
-   - How does your solution specifically addresses the problem.
-
-2. Progress and Challenges faced since Demo #1:
-
-   - Recap: What's your chosen tech stack (code, diagrams, designs, plots, ect)?
-   - Overall, what has been worked on since Demo #1?
-   - What are 3 main sucesses the team is proud of since Demo #1?
-   - What are some major challenges that were encountered? How did you overcome them?
-
-3. Roadmap for the Final Showcase:
-
-   - What do you hope to achieve by the **Final Showcase on April 29th, 2023**?
-   - Where do you sit on your timeline for progression for the above goal?
-   - Are there any challenges you are currently facing or may face?
-   - What resource(s) would be useful to help the team achieve the goal? For example, aid in understanding how to deploy in AWS or the app store from creditable and effective online resources or an industry professional.
-
-4. Any closing thoughts?
-
-May your projects be successful!
-
-![Used By Many People](../used-by.png)
+Coming soon...
\ No newline at end of file
diff --git a/src/projects/demos/README.md b/src/projects/demos/README.md
index 3d22f08..18c7ae7 100644
--- a/src/projects/demos/README.md
+++ b/src/projects/demos/README.md
@@ -1,15 +1,4 @@
-# Demos
+# Demo & Pitch Night 2
+## Early April 2024
 
-At Tech Start UCalgary
-all projects are showcased to the world
-at the end of each academic year.
-In this event, people from different industries and backgrounds
-come and give us feedback on the projects,
-while also allowing you as a professional and us as a club
-to connect and network with different companies.
-
-This year's showcase is scheduled for **April 29th, 2023**.
-To prepare for the showcase
-we want each team to demo their project
-on the last dev night of every month until the showcase.
-Namely, February 2nd, March 16th, and April 6th, all in 2023.
+Coming soon...
\ No newline at end of file