-
Notifications
You must be signed in to change notification settings - Fork 15
Building a profile page
Navigate to the /_members folder in this repository and add a new file to create your bio. The first time you want to contribute to the website, you will be asked to "fork" the repository (you won't need to do this again). This fork is a personal copy of the website into your own Github account. You can then make edits or add files in your forked version of the repository. Once you have finished your changes, head to the pull request tab and click the new pull request button. Be sure to make a pull request on the main website repository as opposed to your forked version. You will then be able to request your changes be included in the main website's repo. This pull request notifies Easton of the request. Don't forget to also update your own repository once the pull request is fulfilled. To do this, click on the Fetch Upstream button found in your forked version and it will update your branch with the newest up to date version. This will make future pull requests easier to navigate.
In terms of profile page specifics, you should use the below example or the example of another member in the lab. You should name your file with the file with your name (e.g., easton-white.md) which will then generate a webpage at https://quantmarineecolab.github.io/members/easton-white.html. You will also want to add an profile picture in the /images folder.
Example:
---
name: Tim Member
image: images/team/some-image.jpg
role: programmer
group: current
description: Senior Programmer
aliases:
- T Member
- T. Member
- Timothy Member
links:
home-page: https://tims-website.com/
email: tim-member@email.com
twitter: tims_twitter
---
A bio for Tim, written in Markdown.
A descriptions of his academic studies, his recent accomplishments, his goals for the future, his likes/dislikes, etc.
One or two paragraphs is probably best.name
Name to show on the team member's page.
image
Url to a portrait photo of the team member.
role
Team member's general role (only options include: "researcher", "undergrad", "grad", "postdoc", "mascot") in your organization. Additional options can be added.
group
Team member's current role (only options include: "current", "alumni") in your organization.
description
Team member's job title/position.
aliases
Team member pages have a link at the bottom that goes to the "Research" page and searches for any papers with the team member's name. This field is a list of aliases or variations of the team member's name to search for that might be cited in papers.
links
Social media links/handles for the team member, without any prefixes like @, www., etc.