Skip to content

Latest commit

 

History

History
55 lines (39 loc) · 2.96 KB

team-members.md

File metadata and controls

55 lines (39 loc) · 2.96 KB
description
How to add, remove, and edit team members

Team members

Add/remove members

To add or remove a team member, create or delete a Markdown file in /_members.

Each file will automatically generate its own page according to its filename. For example, a file with the name tim-member.md will generate a page at /members/tim-member.

{% hint style="info" %} After adding members, you can display them on your site with the list and portrait components. {% endhint %}

Example:

{% code title="tim-member.md" %}

---
name: Tim Member
image: images/team/some-image.jpg
role: programmer
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.

{% endcode %}

ParameterDescription
nameDisplay name of team member.
imageURL to portrait photo of team member.
roleTeam member's role in your organization. Determines the icon and default description text to show.

See /_data/types.yaml for what types of roles are built-in or to add your own.
descriptionDescription of team member's role in your organization. Overrides any default text set from of role.
aliasesBy default, team member pages have a link at the bottom that goes to the "Research" page and searches for any papers by them. This field is a list of aliases/variations/abbreviations of the team member's name to search for.
linksSocial media links for the team member, without any prefixes like @, www., etc.

See /_data/types.yaml for what types of links are built-in or to add your own.

{% hint style="info" %} role vs description

You can organize your team members any way you want with list.md filters and by customizing /_data/types.yaml. However, by default, role is intended to be a high-level type (only a few unique ones in your organization) that you assign an icon and use for coarse list filtering (e.g. "always list PIs first, then postdocs, then undergrads"). description is intended for a more specific description that might be unique to each member. {% endhint %}

Customize member page

The skeleton arrangement and style of team member pages are based on the /_layouts/member.html template, which you can freely edit to your liking.