www
/
www-new
12
3
Fork 5
Code Issues 58 Pull Requests 42 Projects Releases Wiki Activity
Computer Science Club of the University of Waterloo's website. https://csclub.uwaterloo.ca
110 Commits 158 Branches 0 Tags 375 MiB
TypeScript 67.5%
CSS 25.2%
MDX 4.6%
HTML 1.2%
Python 1.1%
Other 0.4%
Go to file
Amy Wang 8d43bf260d
continuous-integration/drone/push Build is passing Details
Fix accessibility issues for keyboard-only users, and fix some Safari bugs (#268) 
Also fixed a couple of Safari-specific bugs. Summary:

- Added a secondary-accent ring around buttons on focus. (White didn't show up very well against the background.) We can always chat with design about this later if we want to change it.
- Fixed the weirdness with tabbing over the headers on the Advice pages. I also made the header flex vertically on mobile screens - this fixes the issue of extra whitespace on the right side, and is also somewhat consistent with the menu-y thing at the top of the mobile Meet the Team page.
	- I was very tempted to do this on the Events term archive pages as well, but I figured I should get someone else's opinion on that first.
- Removed the extra triangle symbol in the MiniEventCard on Safari. I had to use a vendor prefix, but if anyone else can come up with something better, then please do that, thank you.
- Stopped the home page "Computer Science Club" from breaking into two lines on small desktop screens.
- Added extra space to mobile footer.

Closes #250
Closes #248
Closes #253
Closes #256
Closes #261

Co-authored-by: Amy <minds10@hotmail.com>
Co-authored-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
Reviewed-on: #268
Reviewed-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
Co-authored-by: Amy <a258wang@csclub.uwaterloo.ca>
Co-committed-by: Amy <a258wang@csclub.uwaterloo.ca>
 		2021-09-03 16:40:58 -04:00
.vscode Fix constitution formatting (#216) 2021-08-30 09:12:39 -04:00
components Fix accessibility issues for keyboard-only users, and fix some Safari bugs (#268) 2021-09-03 16:40:58 -04:00
content Update Max's blurb (#274) 2021-09-03 16:04:29 -04:00
hooks Meet the Team page (#94) 2021-08-23 11:11:42 -04:00
lib 🚑️ Simplify getCurrentTerm to fix builds around the end of terms 🚑️ (#244) 2021-08-31 23:07:50 -04:00
pages Fix accessibility issues for keyboard-only users, and fix some Safari bugs (#268) 2021-09-03 16:40:58 -04:00
public Add old .ics file and .atom files (#223) 2021-08-30 09:11:55 -04:00
.drone.yml Pass in branch as a custom header to update the website (#178) 2021-08-25 00:24:53 -04:00
.eslintignore Add mdx support and playground 2021-04-26 19:16:55 -04:00
.eslintrc.js Use eslint-plugin-import to bring some order to the mess (#132) 2021-08-13 04:16:37 -04:00
.gitignore Add /events/[year]/[term] page (#158) 2021-08-27 16:14:53 -04:00
README.md Add a minimal README (#218) 2021-08-30 00:50:30 -04:00
check-lockfile.js Move back to package-lock v2 (#176) 2021-08-24 14:42:57 -04:00
deploy-demo.bash Script to deploy site to your CSC website (#99) 2021-08-03 19:17:08 -04:00
next-env.d.ts Upgrade Next, React, TypeScript (#91) 2021-08-01 17:54:25 -04:00
next.config.js Upgrade Next, React, TypeScript (#91) 2021-08-01 17:54:25 -04:00
package-lock.json Move back to package-lock v2 (#176) 2021-08-24 14:42:57 -04:00
package.json Meet the Team page (#94) 2021-08-23 11:11:42 -04:00
postcss.config.json Convert rems to px and use calc to convert on build time 2021-05-24 18:58:28 +00:00
renovate.json Force node 16+ and npm 7+ in renovate (#192) 2021-08-28 00:05:56 -04:00
tsconfig.json Add events archive (#187) 2021-08-28 15:52:45 -04:00
types.d.ts Add /resources/tech-talks and /resources/tech-talks/[slug] (#180) 2021-08-26 00:30:30 -04:00
utils.ts Add events archive (#187) 2021-08-28 15:52:45 -04:00

README.md

Development

Dependencies

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

Local

Production

  • 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)