visiting scientists, exchange students in undergrad, visiting Master's/PhDs etc.

I added the undergraduate section sometime last year but haven't yet integrated all the yaml parsing of the other sections. This fix involves:

• editing members.html to parse the same yaml metadata as presumably the grad student section
• edit the default template structure for a member block in _data/undergrad.yml to include the same tags as grad student section
• update the names (some students listed aren't working with us anymore, and some new students are missing)
  • since no volunteers are working right now, we can wait until after the opening to reconfirm the names, but for now, can update the ones already there

Suggestion

Read data from a Google Sheet using Python to format the yml files.

This will allow any lab member to update their own information in the google sheet at any time, and will automate the process of updating the website via a workflow in GitHub Actions which can be triggered manually, on a schedule (e.g. every few months) and/or after any pushes to the repo.

TODO

• generate collaborative Google Sheet and populate with existing data, created credentials
• find best way to use credentials.json with GitHub while maintaining security (i.e. without uploading the private keys on public repo...make them environment variables?, via github secrets tokens? cannot use a full json in github secrets)
• share access with lab members to update as necessary
• python script using Google Sheets API (some instructions here) to access sheet and update the YAML files in _data/
• create a workflow in GitHub Actions

Do not close this issue.
This allows us to manually trigger updates without pushing to master.

It's just better. I think we had it by date of joining the lab on the old website because either wordpress would just log by date added or it was maybe easier to just append to the end. I originally scraped all the info from franklandlab.com, but we definitely don't need to keep this order on the new website as it's as easy as moving the yaml data around on the new website.

@ridaansari I will get to this at some point, so I just wanted to leave it here as a reminder, but if you wanted to, feel free, but definitely no problem if not, I will aim to do this in the next week or so.

TODO

These are the files we need to update:

• Grad Students
• Post-Docs
• Research Associates
• Staff

Alumni seems to make sense to keep reverse chronological, but open to discussion. The PI list I think is tied to the twitter previews at the bottom, we can keep that the same for now too.

We just need to move each data block in the alphabetical order you want them displayed in each file, making sure to keep at least one blank line between each block.

I don't know if people prefer alphabetical by first or last name. It could be kind of funny to display how many people with names that start with "A" we have.

Alternative Solution:

Sort by field in Jekyll rather than order written in YAML file, see this SO answer. Main reason why this would be better is to reduce the chance for typos and breaking errors in the syntax (too much too little white space/tabbing) when having to insert of move items around, rather than appending to the end.