Just edit files in contents/ and then commit the change, it will automatically deploy in 5 mins.
- 
Add an item at
contents/seminars/seminar.yaml - 
Commit the change directly to the
masterbranch 
- 
Add an item at
contents/research/pubs.yaml - 
Add image for publication (optional)
- Add image under 
contents/research/<year>/<venue>to keep images organized - Image path would then be of the form 
<year>/<venue>/<imageName> 
 - Add image under 
 - 
Commit the change directly to the
masterbranch 
- 
Add an item at
contents/research/news.yaml- Add image under 
contents/research/<year>to keep images organized - Add information about the news item (e.g. 
description,image, andurl) as appropriate - Specify 
type: conferencefor conference news (this will include publications for that conference) 
 - Add image under 
 - 
If conference news, update publication items (see above) and add entry for
workshops(if there are workshops we are organizing / participating in) - 
Commit the change directly to the
masterbranch 
- 
Upload the images to
contents/carousel - 
Commit the change directly to the
masterbranch 
- 
Upload the image to
contents/people - 
Add an item at
contents/people/people.yaml - 
Commit the change directly to the
masterbranch 
- 
Make change to
contents/whysfu.yaml - 
Commit the change directly to the
masterbranch 
This website is developed using Vue 2.
For local testing you will need to have nodejs.
Use nvm to select a version of node to use. The build has been tested with node v14 to v18.
To download and install node.js v18.20.4:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
source ~/.bashrc
nvm install v18.20.4
Build src/assets/data.json from yaml files (not sure why yaml files are not used directly).  You will need to have python3 installed.
pip3 install pyyaml                         # Install dependencies
python3 src/assets/parse_content.py         # Parse content
Run local server (may need to switch package.json "webpack-dev-server": "^2.11.2")
npm install              # install node modules            
npm start                # Start server
Go to http://localhost:8080
Contact Patrick at me@haoxp.xyz
Looks like once in a while the Github gods require us to generate a new token. The basic procedure involves two steps.
- Generate a new github token
 - Update it on Travis by setting the 
GITHUB_TOKENenvironment variable to contain the new token.