diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
deleted file mode 100644
index 46c150e15..000000000
--- a/.github/pull_request_template.md
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-**Volunteers: Are you marking this coursework?** _You can find a guide on how to mark this coursework in `HOW_TO_MARK.md` in the root of this repository_
-
-# Your Details
-
-- Your Name:
-- Your City:
-- Your Slack Name:
-
-# Homework Details
-
-- Module:
-- Week:
-
-# Notes
-
-- What did you find easy?
-
-- What did you find hard?
-
-- What do you still not understand?
-
-- Any other notes?
diff --git a/.github/workflows/close.yml b/.github/workflows/close.yml
deleted file mode 100644
index 137dc57e9..000000000
--- a/.github/workflows/close.yml
+++ /dev/null
@@ -1,17 +0,0 @@
-name: "Close stale issues and PRs"
-on:
- workflow_dispatch:
- schedule:
- - cron: "30 1 * * *"
-
-jobs:
- stale:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/stale@v3
- with:
- stale-pr-message: "Your coursework submission has been closed because nobody has interacted with it in six weeks. You are welcome to re-open it to get more feedback."
- days-before-stale: 42
- days-before-close: 0
- days-before-issue-stale: -1
- days-before-issue-close: -1
diff --git a/GRADING.md b/GRADING.md
deleted file mode 100644
index b8ab587d2..000000000
--- a/GRADING.md
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-# Grading
-
-All coursework is graded using the Marking Guide found on the Syllabus.
-
-http://syllabus.codeyourfuture.io/guides/marking-guide
-
-If you have any questions on these guidelines - please ask.
-
-## Coding Standards
-
-Your code should follow our Coding Standards or it will be marked poorly.
-
-https://syllabus.codeyourfuture.io/guides/code-style-guide
diff --git a/HOW-TO-GET-HELP.md b/HOW-TO-GET-HELP.md
deleted file mode 100644
index f2ebef1c8..000000000
--- a/HOW-TO-GET-HELP.md
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-# How To Get Help
-
-When you get stuck it's important that you ask for help at the right time and in the right way - this means you will be able to solve your problem as quickly as possible!
-
-## Guide
-
-Please review our guide on the Syllabus for how to get help
-
-https://syllabus.codeyourfuture.io/guides/escalation-policy/
-
-You should complete all of the steps in the order listed to get help
-
-## Reporting Issues in Coursework
-
-Is there a problem with this coursework?
-Have you noticed a bug?
-Does something not make sense?
-
-Post in the relevent channel on Slack depending on the module you are completing:
-
-- Git - `cyf-module-git`
-- HTML/CSS - `cyf-module-html-css`
-- JavaScript Core 1 - `cyf-module-js1`
-- JavaScript Core 2 - `cyf-module-js2`
-- JavaScript Core 2 - `cyf-module-js3`
-- React - `cyf-module-react`
-- Node - `cyf-module-node`
-- SQL - `cyf-module-sql`
-- MongoDB - `cyf-module-mongodb`
-
-None of these? Post in #cyf-syllabus.
diff --git a/HOW-TO-SUBMIT.md b/HOW-TO-SUBMIT.md
deleted file mode 100644
index f9430423a..000000000
--- a/HOW-TO-SUBMIT.md
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-# How To Submit Your Coursework
-
-You should use Git & Github to submit your coursework as a pull request.
-
-You can use the Github Desktop cheatsheet here to help you do this.
-
-[Github Desktop Cheatsheet](http://syllabus.codeyourfuture.io/git/cheatsheet)
-
-You can also use this lesson to help you submit your coursework.
-
-[Git Lesson](http://syllabus.codeyourfuture.io/git/index)
-
-## Questions & Help
-
-Not being able to submit your coursework is not an excuse for not doing it.
-
-If you cannot submit your coursework you **must** message us on Slack to get help.
diff --git a/HOW_TO_MARK.md b/HOW_TO_MARK.md
deleted file mode 100644
index bc72d1949..000000000
--- a/HOW_TO_MARK.md
+++ /dev/null
@@ -1,64 +0,0 @@
-
-
-_This file is useful for Volunteers only_
-
-## 1) Solutions
-
-### 1.1) Where to find solutions?
-
-You can find the solution to this coursework in a repository with the same name as this but with `-Solution` after the name.
-
-For example, for this repo:
-
-https://github.com/CodeYourFuture/JavaScript-Core-1-Coursework-Week1
-
-The solutions would be found in:
-
-https://github.com/CodeYourFuture/JavaScript-Core-1-Coursework-Week1-Solution
-
-**If you do not have access to these repositories** then please contact your City Coordinator to get access to our Github Team.
-
-### 1.2) Using the Solutions Repo
-
-In these repositories you will find solutions to each week's coursework. These solutions are example answers and will not be the exact solution that students give. You should use it to inform your feedback of the coursework.
-
-Additionally, you will find marking guides in these places
-
-- The `marking` folder - Used to store multiple guides on marking
-- `marking.md` file - Used to store notes on common problems we're trying to address
-- `solutions.md` - A file used by students for notes on best practice
-
-## 2) Before You Start
-
-### 2.1) Feedback Guide
-
-A guide for marking coursework can be found here. Please read it before you start.
-
-https://docs.codeyourfuture.io/teams/education/homework-feedback
-
-### 2.2) Marking Guide
-
-Here is a useful resources you can direct students to when you see them have common mistakes
-
-https://syllabus.codeyourfuture.io/guides/marking-guide
-
-This guide should be used when you see a student making a common mistake so instead of writing out a reply you can send them to the a good resource.
-
-For example, if the student is leaving in lots of commented out code you could write
-
-```txt
-Great work so far!
-
-It's best if you remove code that you're not using, you can read more about this here
-https://syllabus.codeyourfuture.io/guides/marking-guide#commented-out-code
-```
-
-### 3.3) Style Guide
-
-All code at CYF should follow this Style Guide
-
-https://syllabus.codeyourfuture.io/guides/code-style-guide/
diff --git a/README.md b/README.md
deleted file mode 100644
index 31db35cef..000000000
--- a/README.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# karma-clone
-
-The aim of this exercise is to create a page that looks just like this one:
-
-
-
-### Set up
-
- - **Fork and clone** this repo.
- - To fork, hit the 'fork' button in the top right corner of this page on Github.
- Now you should be on your own Github repository - you'll know this because your name should now be in the repo name at the top of the Github page.
- - To clone, click the green button that says 'Code' on that page.
- Now the code is on your own machine (this happened when you cloned), AND it's linked to your own Karma repository on Github (which was created when you forked).
-
-# Instructions
-
- - **Edit `index.html` and `style.css`** to re-create the design above.
- - Remember, use semantic HTML to re-create the structure, and style each element using CSS to make a perfect copy of the above image.
- - All the images and icons you need can be found in the `img` folder, and the font 'Roboto' is already loaded into the project.
- - **Only create the desktop design** for now.
-
-### Submitting your work
- - **Commit and push your code often** (for example every half an hour)so you get into the habit and you avoid losing any code that you write if your machine crashes for example.
- - Once you're ready to submit your homework for review, do a final push and **create a Pull Request**. If you're unsure how to do this, [have a look here](https://syllabus.codeyourfuture.io/git/cheatsheet/#i-want-to-send-my-code-to-volunteers-pushing).
-
diff --git a/css/normalize.css b/css/normalize.css
deleted file mode 100755
index 957605911..000000000
--- a/css/normalize.css
+++ /dev/null
@@ -1,436 +0,0 @@
-
-/**
- * ---------------------------------------
- * DO NOT EDIT THIS FILE.
- * All your styling should go in style.css
- * ---------------------------------------
- */
-
-
-/*! normalize.css v3.0.2 | MIT License | git.io/normalize */
-
-/**
- * 1. Set default font family to sans-serif.
- * 2. Prevent iOS text size adjust after orientation change, without disabling
- * user zoom.
- */
-
-html {
- font-family: sans-serif; /* 1 */
- -ms-text-size-adjust: 100%; /* 2 */
- -webkit-text-size-adjust: 100%; /* 2 */
-}
-
-/**
- * Remove default margin.
- */
-
-body {
- margin: 0;
-}
-
-/* HTML5 display definitions
- ========================================================================== */
-
-/**
- * Correct `block` display not defined for any HTML5 element in IE 8/9.
- * Correct `block` display not defined for `details` or `summary` in IE 10/11
- * and Firefox.
- * Correct `block` display not defined for `main` in IE 11.
- */
-
-article,
-aside,
-details,
-figcaption,
-figure,
-footer,
-header,
-hgroup,
-main,
-menu,
-nav,
-section,
-summary {
- display: block;
-}
-
-/**
- * 1. Correct `inline-block` display not defined in IE 8/9.
- * 2. Normalize vertical alignment of `progress` in Chrome, Firefox, and Opera.
- */
-
-audio,
-canvas,
-progress,
-video {
- display: inline-block; /* 1 */
- vertical-align: baseline; /* 2 */
-}
-
-/**
- * Prevent modern browsers from displaying `audio` without controls.
- * Remove excess height in iOS 5 devices.
- */
-
-audio:not([controls]) {
- display: none;
- height: 0;
-}
-
-/**
- * Address `[hidden]` styling not present in IE 8/9/10.
- * Hide the `template` element in IE 8/9/11, Safari, and Firefox < 22.
- */
-
-[hidden],
-template {
- display: none;
-}
-
-/* Links
- ========================================================================== */
-
-/**
- * Remove the gray background color from active links in IE 10.
- */
-
-a {
- background-color: transparent;
-}
-
-/**
- * Improve readability when focused and also mouse hovered in all browsers.
- */
-
-a:active,
-a:hover {
- outline: 0;
-}
-
-/* Text-level semantics
- ========================================================================== */
-
-/**
- * Address styling not present in IE 8/9/10/11, Safari, and Chrome.
- */
-
-abbr[title] {
- border-bottom: 1px dotted;
-}
-
-/**
- * Address style set to `bolder` in Firefox 4+, Safari, and Chrome.
- */
-
-b,
-strong {
- font-weight: bold;
-}
-
-/**
- * Address styling not present in Safari and Chrome.
- */
-
-dfn {
- font-style: italic;
-}
-
-/**
- * Address variable `h1` font-size and margin within `section` and `article`
- * contexts in Firefox 4+, Safari, and Chrome.
- */
-
-h1 {
- font-size: 2em;
- margin: 0.67em 0;
-}
-
-/**
- * Address styling not present in IE 8/9.
- */
-
-mark {
- background: #ff0;
- color: #000;
-}
-
-/**
- * Address inconsistent and variable font size in all browsers.
- */
-
-small {
- font-size: 80%;
-}
-
-/**
- * Prevent `sub` and `sup` affecting `line-height` in all browsers.
- */
-
-sub,
-sup {
- font-size: 75%;
- line-height: 0;
- position: relative;
- vertical-align: baseline;
-}
-
-sup {
- top: -0.5em;
-}
-
-sub {
- bottom: -0.25em;
-}
-
-/* Embedded content
- ========================================================================== */
-
-/**
- * Remove border when inside `a` element in IE 8/9/10.
- */
-
-img {
- border: 0;
-}
-
-/**
- * Correct overflow not hidden in IE 9/10/11.
- */
-
-svg:not(:root) {
- overflow: hidden;
-}
-
-/* Grouping content
- ========================================================================== */
-
-/**
- * Address margin not present in IE 8/9 and Safari.
- */
-
-figure {
- margin: 1em 40px;
-}
-
-/**
- * Address differences between Firefox and other browsers.
- */
-
-hr {
- -moz-box-sizing: content-box;
- box-sizing: content-box;
- height: 0;
-}
-
-/**
- * Contain overflow in all browsers.
- */
-
-pre {
- overflow: auto;
-}
-
-/**
- * Address odd `em`-unit font size rendering in all browsers.
- */
-
-code,
-kbd,
-pre,
-samp {
- font-family: monospace, monospace;
- font-size: 1em;
-}
-
-/* Forms
- ========================================================================== */
-
-/**
- * Known limitation: by default, Chrome and Safari on OS X allow very limited
- * styling of `select`, unless a `border` property is set.
- */
-
-/**
- * 1. Correct color not being inherited.
- * Known issue: affects color of disabled elements.
- * 2. Correct font properties not being inherited.
- * 3. Address margins set differently in Firefox 4+, Safari, and Chrome.
- */
-
-button,
-input,
-optgroup,
-select,
-textarea {
- color: inherit; /* 1 */
- font: inherit; /* 2 */
- margin: 0; /* 3 */
-}
-
-/**
- * Address `overflow` set to `hidden` in IE 8/9/10/11.
- */
-
-button {
- overflow: visible;
-}
-
-/**
- * Address inconsistent `text-transform` inheritance for `button` and `select`.
- * All other form control elements do not inherit `text-transform` values.
- * Correct `button` style inheritance in Firefox, IE 8/9/10/11, and Opera.
- * Correct `select` style inheritance in Firefox.
- */
-
-button,
-select {
- text-transform: none;
-}
-
-/**
- * 1. Avoid the WebKit bug in Android 4.0.* where (2) destroys native `audio`
- * and `video` controls.
- * 2. Correct inability to style clickable `input` types in iOS.
- * 3. Improve usability and consistency of cursor style between image-type
- * `input` and others.
- */
-
-button,
-html input[type="button"], /* 1 */
-input[type="reset"],
-input[type="submit"] {
- -webkit-appearance: button; /* 2 */
- cursor: pointer; /* 3 */
-}
-
-/**
- * Re-set default cursor for disabled elements.
- */
-
-button[disabled],
-html input[disabled] {
- cursor: default;
-}
-
-/**
- * Remove inner padding and border in Firefox 4+.
- */
-
-button::-moz-focus-inner,
-input::-moz-focus-inner {
- border: 0;
- padding: 0;
-}
-
-/**
- * Address Firefox 4+ setting `line-height` on `input` using `!important` in
- * the UA stylesheet.
- */
-
-input {
- line-height: normal;
-}
-
-/**
- * It's recommended that you don't attempt to style these elements.
- * Firefox's implementation doesn't respect box-sizing, padding, or width.
- *
- * 1. Address box sizing set to `content-box` in IE 8/9/10.
- * 2. Remove excess padding in IE 8/9/10.
- */
-
-input[type="checkbox"],
-input[type="radio"] {
- box-sizing: border-box; /* 1 */
- padding: 0; /* 2 */
-}
-
-/**
- * Fix the cursor style for Chrome's increment/decrement buttons. For certain
- * `font-size` values of the `input`, it causes the cursor style of the
- * decrement button to change from `default` to `text`.
- */
-
-input[type="number"]::-webkit-inner-spin-button,
-input[type="number"]::-webkit-outer-spin-button {
- height: auto;
-}
-
-/**
- * 1. Address `appearance` set to `searchfield` in Safari and Chrome.
- * 2. Address `box-sizing` set to `border-box` in Safari and Chrome
- * (include `-moz` to future-proof).
- */
-
-input[type="search"] {
- -webkit-appearance: textfield; /* 1 */
- -moz-box-sizing: content-box;
- -webkit-box-sizing: content-box; /* 2 */
- box-sizing: content-box;
-}
-
-/**
- * Remove inner padding and search cancel button in Safari and Chrome on OS X.
- * Safari (but not Chrome) clips the cancel button when the search input has
- * padding (and `textfield` appearance).
- */
-
-input[type="search"]::-webkit-search-cancel-button,
-input[type="search"]::-webkit-search-decoration {
- -webkit-appearance: none;
-}
-
-/**
- * Define consistent border, margin, and padding.
- */
-
-fieldset {
- border: 1px solid #c0c0c0;
- margin: 0 2px;
- padding: 0.35em 0.625em 0.75em;
-}
-
-/**
- * 1. Correct `color` not being inherited in IE 8/9/10/11.
- * 2. Remove padding so people aren't caught out if they zero out fieldsets.
- */
-
-legend {
- border: 0; /* 1 */
- padding: 0; /* 2 */
-}
-
-/**
- * Remove default vertical scrollbar in IE 8/9/10/11.
- */
-
-textarea {
- overflow: auto;
-}
-
-/**
- * Don't inherit the `font-weight` (applied by a rule above).
- * NOTE: the default cannot safely be changed in Chrome and Safari on OS X.
- */
-
-optgroup {
- font-weight: bold;
-}
-
-/* Tables
- ========================================================================== */
-
-/**
- * Remove most spacing between table cells.
- */
-
-table {
- border-collapse: collapse;
- border-spacing: 0;
-}
-
-td,
-th {
- padding: 0;
-}
\ No newline at end of file
diff --git a/css/style.css b/css/style.css
deleted file mode 100755
index 5cb025cef..000000000
--- a/css/style.css
+++ /dev/null
@@ -1,19 +0,0 @@
-
- /* We are using the 'Roboto' font from Google. This has already been added to your HTML header */
-
-body {
- font-family: 'Roboto', sans-serif;
- -webkit-font-smoothing: antialiased;
-}
-
-/**
- * Add your custom styles below
- *
- * Remember:
- * - Be organised, use comments and separate your styles into meaningful chunks
- * for example: General styles, Navigation styles, Hero styles, Footer etc.
- *
- * - When using Flexbox, remember the items you want to move around need to be inside a parent container set to 'display: flex'
- */
-
-
diff --git a/favicon.ico b/favicon.ico
deleted file mode 100755
index 286aa3d4d..000000000
Binary files a/favicon.ico and /dev/null differ
diff --git a/homepage-desktop.png b/homepage-desktop.png
deleted file mode 100644
index 06b4f8b37..000000000
Binary files a/homepage-desktop.png and /dev/null differ
diff --git a/img/facebook-icon.svg b/img/facebook-icon.svg
deleted file mode 100644
index b3e551475..000000000
--- a/img/facebook-icon.svg
+++ /dev/null
@@ -1,5 +0,0 @@
-
\ No newline at end of file
diff --git a/img/first-background.jpg b/img/first-background.jpg
deleted file mode 100755
index 5d619e25f..000000000
Binary files a/img/first-background.jpg and /dev/null differ
diff --git a/img/icon-coffee.svg b/img/icon-coffee.svg
deleted file mode 100755
index 424d88ada..000000000
--- a/img/icon-coffee.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-
\ No newline at end of file
diff --git a/img/icon-devices.svg b/img/icon-devices.svg
deleted file mode 100755
index 8e4806e87..000000000
--- a/img/icon-devices.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-
\ No newline at end of file
diff --git a/img/icon-refill.svg b/img/icon-refill.svg
deleted file mode 100755
index 2f2a4f1ee..000000000
--- a/img/icon-refill.svg
+++ /dev/null
@@ -1,6 +0,0 @@
-
\ No newline at end of file
diff --git a/img/instagram-icon.svg b/img/instagram-icon.svg
deleted file mode 100644
index 56e207086..000000000
--- a/img/instagram-icon.svg
+++ /dev/null
@@ -1,18 +0,0 @@
-
\ No newline at end of file
diff --git a/img/karma-logo.svg b/img/karma-logo.svg
deleted file mode 100755
index d550e81d8..000000000
--- a/img/karma-logo.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-
\ No newline at end of file
diff --git a/img/twitter-icon.svg b/img/twitter-icon.svg
deleted file mode 100644
index a480cdbec..000000000
--- a/img/twitter-icon.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-
\ No newline at end of file
diff --git a/index.html b/index.html
deleted file mode 100755
index 3e742ef04..000000000
--- a/index.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
- Karma
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/level-2/README.md b/level-2/README.md
deleted file mode 100644
index 1d1e538e8..000000000
--- a/level-2/README.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# karma-clone
-## Level 2
-The aim of this exercise is to:
-- add a new section to the homepage
-- create a new 'store' page with an order form
-- connect the 2 pages together by adding navigation
-
-# Instructions
-
-- You'll find the designs inside the 'level-2' folder.
-- Add the new section in your `index.html`
-- Create a new page called `store.html` and re-create the design for the store page (the design is `level-2/store-desktop.png`)
-- For the store page styles, you can keep using the same `style.css` file and add your store page styles in there.
-You could also create a specific `store.css` file, but make sure you don't repeat the CSS already in `style.css`!
-- Connect the 2 pages by:
- - making the homepage's "Get Karma today" button navigate to the store page.
- - making the header navigation "Store" link navigate to the store page, and the "Meet Karma" link navigate to the homepage.
-
-### Stretch goal
-
-**Custom radio buttons and checkbox**
-
-The 2 radio buttons and the checkbox in the store page design are tricky to style and will require you to do a little research. Focus on the rest of the form and layout first, and leave these until the end as a stretch goal.
-
-## Submitting your work
- - Remember to **commit and push your code often**
- - Once you're ready to submit your homework for review, do a final push and **create a Pull Request**. If you're unsure how to do this, [have a look here](https://syllabus.codeyourfuture.io/git/cheatsheet/#i-want-to-send-my-code-to-volunteers-pushing).
- **Note:** If you've added your level 2 code to the same branch, then it will just update your previous Pull Request and you won't need a new PR.
-
-## Designs
-
-
-
-
-
diff --git a/level-2/checkmark.svg b/level-2/checkmark.svg
deleted file mode 100644
index 17a3c14f3..000000000
--- a/level-2/checkmark.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
diff --git a/level-2/homepage-desktop-extended.png b/level-2/homepage-desktop-extended.png
deleted file mode 100644
index 6ebe959ca..000000000
Binary files a/level-2/homepage-desktop-extended.png and /dev/null differ
diff --git a/level-2/homepage-feature.png b/level-2/homepage-feature.png
deleted file mode 100644
index 3500b2e4c..000000000
Binary files a/level-2/homepage-feature.png and /dev/null differ
diff --git a/level-2/store-desktop.png b/level-2/store-desktop.png
deleted file mode 100644
index 441382b1b..000000000
Binary files a/level-2/store-desktop.png and /dev/null differ
diff --git a/level-2/store-image_by-andrew-neel-unsplash.jpg b/level-2/store-image_by-andrew-neel-unsplash.jpg
deleted file mode 100644
index a8ad89099..000000000
Binary files a/level-2/store-image_by-andrew-neel-unsplash.jpg and /dev/null differ
diff --git a/level-3/README.md b/level-3/README.md
deleted file mode 100644
index 5dc5831af..000000000
--- a/level-3/README.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# karma-clone
-## Level 3
-
-Now let's make this website responsive!
-
-# Instructions
-
-- Use media queries to make both the homepage and the order page look good on mobile.
-- You'll find the mobile designs inside the 'level-3' folder.
-- You can use 1 or 2 breakpoints, it's up to you (if you're not sure, start with 768px - it's a classic one as it's the width of an iPad and a good point to switch from a mobile layout to a desktop layout).
-- You might have to change some of your existing HTML and CSS code so that your webpage can match the mobile and desktop designs
-
-### Submitting your work
- - Remember to **commit and push your code often**
- - Once you're ready to submit your homework for review, do a final push and **create a Pull Request**. If you're unsure how to do this, [have a look here](https://syllabus.codeyourfuture.io/git/cheatsheet/#i-want-to-send-my-code-to-volunteers-pushing).
- **Note:** If you've added your level 3 code to the same branch you used for the previous levels, then it will just update your existing Pull Request and you won't need a new PR.
-
-## Designs
-
-
-
-
diff --git a/level-3/homepage-mobile.png b/level-3/homepage-mobile.png
deleted file mode 100644
index bbf49ff15..000000000
Binary files a/level-3/homepage-mobile.png and /dev/null differ
diff --git a/level-3/menu-hamburger.svg b/level-3/menu-hamburger.svg
deleted file mode 100644
index d97acc7ff..000000000
--- a/level-3/menu-hamburger.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
diff --git a/level-3/store-mobile.png b/level-3/store-mobile.png
deleted file mode 100644
index db48cab47..000000000
Binary files a/level-3/store-mobile.png and /dev/null differ