Managing Staff

Staff records live in _data/staff.yml. They supply public profiles, department teams, social links, and news author information.

Set up a staff record

Public profile example

exampleperson:
  aboutpage: true
  department: "Unity"
  pfp: /assets/staffpfp/example-person.png
  path: /staff/exampleperson
  socials:
    github: https://github.com/example
  en-us:
    name: Example Person
    role: Example Role
    bio: A short public biography.
  zh-cn:
    name: 示例人员
    role: 示例职位
    bio: 一段简短的公开简介。

exampleperson is the person's stable identifier. News articles use it as their author value. Do not rename it without updating every article that refers to it.

Public and private records

A record with aboutpage: true appears publicly and requires:

• pfp, beginning with / and pointing to an existing image;
• path, pointing to the matching public profile;
• name, role, and bio under every configured language key.

socials is optional. Only add public, approved HTTPS links. See Localization for the multilingual data pattern.

A placeholder or private record uses aboutpage: false. It must not be displayed as a public staff profile.

Match a department

The staff record's department must exactly match a staff_department value in _data/departments.yml. Capitalization matters.

The owner uses the special Owner group. Other staff should use the appropriate department value.

Staff who write news

An article uses the short identifier, not the display name:

author: exampleperson

See Publishing News for the full article format.

Verify the profile

Check the result

• Open /staff, /zh-cn/staff, and both versions of the matching department page locally.
• Confirm that public profiles appear once and private records do not appear.
• Check the picture, role, biography, and social links.
• If the person is an author, preview one of their articles.
• Run Running Checks.

Return to Managing Site Data.