This is the ASSETS repo for our conference websites. The repo was started in 2021 by Professor Jon E. Froehlich and the ASSETS'22 Web/Design team (Jaylin Herskovitz, Liang He, Judy Kong, and Jason Wu) to:
- Help others more easily build off the brand new, fully accessible ASSETS'22 website created by @jayhersk, @EdigaHe, @judykong97, js0nwu, and @jonfroehlich. 🙏🏽
- Better track and code share between previous ASSETS websites more generally dating back to ASSETS'18 💻
If you are a new Web/Design Co-chair for ASSETS (woohoo, that's awesome), here's what you need to do:
-
First, email jonf@cs.uw.edu to get access to this repo. Please CC your conference chair.
-
Second, you'll want to create your own repo (say, assets2024). You can do this by forking one of the existing repos (e.g., assets2022) or by manually creating assets2024 and committing code piece-by-piece. Given that in 2022, we completely redesigned the ASSETS website experience to improve both aesthetics and accessibility, it's likely easiest to start either with the ASSETS'22 codebase or the ASSETS'23 codebase (ASSETS'23 started as a fork of ASSETS'22 but I haven't tracked that code, so not sure if they made significant changes).
-
Third, deploy your website on to ACM servers. Unfortunately, you have to do this manually using SFTP (yes, for every change). For ASSETS'22, we had the following setup:
- A test server at: https://assets-conference.github.io/assets2022/, which is incredibly easy to setup using GitHub Pages. This allowed us to test out changes before deploying them to ACM.
- A production server at: https://assets22.sigaccess.org/