Just edit files in contents/
and then commit the change, it will automatically deploy in 5 mins.
-
Upload the images to
contents/carousel
-
Commit the change directly to the
master
branch
-
Upload the image to
contents/people
-
Add an item at
contents/people/people.yaml
-
Commit the change directly to the
master
branch
-
Add an item at
contents/seminars/seminar.yaml
-
Commit the change directly to the
master
branch
-
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
- Add image under
-
If publications news, add items at
contents/research/pubs.yaml
- 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
master
branch
-
Make change to
contents/whysfu.yaml
-
Commit the change directly to the
master
branch
Build src/assets/data.json
from yaml files (not sure why yaml files are not used directly)
pip3 install pyyaml
python3 src/assets/parse_content.py
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_TOKEN
environment variable to contain the new token.