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.
j285he 61cefde5b1 Change about content (#326) 1 day ago
.vscode Fix constitution formatting (#216) 3 weeks ago
components Fix Organized Content Arrows (#318) 1 day ago
content Change about content (#326) 1 day ago
hooks Meet the Team page (#94) 4 weeks ago
lib add news event for resume review event (#313) 6 days ago
pages Clean up Shapes Backgrounds on some mobile pages (#307) 6 days ago
public add links to network interface graphs 1 week ago
.drone.yml force IPv4 for SSH 1 week ago
.eslintignore Add mdx support and playground 5 months ago
.eslintrc.js Use eslint-plugin-import to bring some order to the mess (#132) 1 month ago
.gitignore Initial commit 🎉 5 months ago Final changes for deploying (#279) 3 weeks ago
check-lockfile.js Move back to package-lock v2 (#176) 4 weeks ago
deploy-demo.bash Script to deploy site to your CSC website (#99) 2 months ago increase processes ulimit 1 week ago
next-env.d.ts Upgrade Next, React, TypeScript (#91) 2 months ago
next.config.js Update content for advice pages (#299) 1 week ago
package-lock.json Add [event].tsx page (#153) 1 month ago
package.json Meet the Team page (#94) 4 weeks ago
postcss.config.json Convert rems to px and use calc to convert on build time 4 months ago
renovate.json Force node 16+ and npm 7+ in renovate (#192) 4 weeks ago
tsconfig.json Add events archive (#187) 3 weeks ago
types.d.ts Add permalink in event card (#316) 1 week ago
utils.ts Add events archive (#187) 3 weeks 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)


  • groups (make sure you're in the www group)
  • curl -o- | bash (run on caffeine)