Computer Science Club of the University of Waterloo's website.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
William Tran 75bddd63f9 COC-page-updates (#240) 2 years ago
.vscode Fix constitution formatting (#216) 2 years ago
components Fix navbar highlight for Organized Content sections (#182) 2 years ago
content COC-page-updates (#240) 2 years ago
hooks Meet the Team page (#94) 2 years ago
lib 🚑️ Simplify getCurrentTerm to fix builds around the end of terms 🚑️ (#244) 2 years ago
pages Fix past events rendered twice (#245) 2 years ago
public Add old .ics file and .atom files (#223) 2 years ago
.drone.yml Pass in branch as a custom header to update the website (#178) 2 years ago
.eslintignore Add mdx support and playground 2 years ago
.eslintrc.js Use eslint-plugin-import to bring some order to the mess (#132) 2 years ago
.gitignore Add /events/[year]/[term] page (#158) 2 years ago Add a minimal README (#218) 2 years ago
check-lockfile.js Move back to package-lock v2 (#176) 2 years ago
deploy-demo.bash Script to deploy site to your CSC website (#99) 2 years ago
next-env.d.ts Upgrade Next, React, TypeScript (#91) 2 years ago
next.config.js Upgrade Next, React, TypeScript (#91) 2 years ago
package-lock.json Move back to package-lock v2 (#176) 2 years ago
package.json Meet the Team page (#94) 2 years ago
postcss.config.json Convert rems to px and use calc to convert on build time 2 years ago
renovate.json Force node 16+ and npm 7+ in renovate (#192) 2 years ago
tsconfig.json Add events archive (#187) 2 years ago
types.d.ts Add /resources/tech-talks and /resources/tech-talks/[slug] (#180) 2 years ago
utils.ts Add events archive (#187) 2 years ago



Make sure that you have node >= 14 and npm >= 7. Node 14 ships with npm v6, so if you're using node 14, you would need to upgrade npm. Alternatively you could also upgrade to node 16, which ships with npm 7.

How to upgrade npm: npm i -g npm



  • npm install to install project dependencies
  • npm run build to generate html/css/js
  • npm run export to move the built files (along with assets in the public directory) to the /out directory
  • Use your favourite web server to host the files in the /out directory. (A very simple one would be python -m http.server - not sure if it should actually be used for production :P)