# Team members

## Add/remove members

To add or remove a team member, create or delete a Markdown file in `/_members`.&#x20;

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](https://greene-lab.gitbook.io/lab-website-template-docs/basics/components/list) and [portrait](https://greene-lab.gitbook.io/lab-website-template-docs/basics/components/portrait) components.
{% endhint %}

Example:

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

```markdown
---
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 %}

<table><thead><tr><th width="199">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><code>name</code></td><td>Display name of team member.</td></tr><tr><td><code>image</code></td><td>URL to portrait photo of team member.</td></tr><tr><td><code>role</code></td><td>Team member's role in your organization. Determines the <a href="components/icon">icon</a> and <em>default</em> description text to show.<br><br>See <code>/_data/types.yaml</code> for what types of roles are built-in or to add your own.</td></tr><tr><td><code>description</code></td><td>Description of team member's role in your organization. Overrides any default text set from of  <code>role</code>.</td></tr><tr><td><code>aliases</code></td><td>By 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.</td></tr><tr><td><code>links</code></td><td>Social media links for the team member, without any prefixes like <code>@</code>, <code>www.</code>, etc.<br><br>See <code>/_data/types.yaml</code> for what types of links are built-in or to add your own.</td></tr></tbody></table>

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

You can organize your team members any way you want with [list](https://greene-lab.gitbook.io/lab-website-template-docs/basics/components/list "mention") 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://greene-lab.gitbook.io/lab-website-template-docs/basics/team-members.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
