Editing staff and officer pages

Staff pages guide

Why the roster matters

Players use the staff page when something goes wrong: ban appeals, reports, “who do I talk to?” Leaving demo names (“Mara Voss”, “Oxide” placeholders) signals the site was never finished. Keeping three real people with clear roles beats a grid of twelve fictional bios.

Remember: GameSignal hosts the website. In-game admin permissions live on the game server. The page should match Discord roles closely enough that applicants are not messaging the wrong person.

Open staff.html

In VS Code, open the template folder and select staff.html. Preview it in a browser beside the editor. Community name in the header still comes from js/config.js — you do not retype the brand on every card. Full config notes: Edit Templates.

Some designs use initials-only cards; premium layouts like Ashfall use photo cards with role badges and short bios. The HTML class names differ slightly, but the idea is the same: one repeated block per person inside a grid.

Anatomy of a staff card

A typical card includes:

• Display name (what players should call them)
• Role label — Owner, Admin, Moderator, Officer, Media, etc.
• Optional Discord handle or timezone
• Optional short bio (one or two sentences)
• Optional portrait image or initials avatar

Change the text inside the existing tags. Avoid deleting wrapping <article> or grid classes unless you are removing the whole person — stripped wrappers break spacing on mobile.

Add and remove people

1. Copy one complete staff card block (from the opening <article to its closing tag).
2. Paste it before the grid’s closing container.
3. Edit name, role, handle, bio and image for the new person.
4. To remove someone, delete their entire card block — do not leave empty shells.

Order cards the way you want them seen: founders first, then ops, then moderators is a common pattern. Players skim left-to-right; put the appeal contact somewhere obvious if that is not the owner.

Roles that match reality

Use the titles your Discord already uses. Inventing “Head of Narrative Continuity” for a two-admin Rust wipe server wastes space. If someone only helps on weekends, say Moderator — not Admin — so expectations stay fair.

When someone steps down, remove them in the same week you remove Discord roles. Out-of-date officer lists cause drama during raids and reports. Put a calendar reminder after major roster changes if multiple people edit the site.

Portraits and initials

Photo cards: replace the image file under assets/images/ while keeping the same filename, or export a new file and update the src. Crop faces roughly centred; huge uncropped screenshots look messy in square frames. Compress in GIMP before upload — staff grids with six multi‑megabyte JPEGs slow phones.

Initials-only templates: change the letters and background classes if the design provides role colour variants. Keep alt text meaningful when an image is present (“Portrait of …”).

Only publish photos people agreed to show publicly. Discord avatars are not automatically licensed for the marketing site.

Recruiting / contact CTAs

Many staff pages end with a “join the crew” or “open a ticket” section. Point those buttons at your Discord invite through config.js (see Discord links). If you are not hiring staff, rewrite that band into “Need help? Open a ticket” so it does not look like a fake hiring drive.

After edits, upload staff.html and any new images via cPanel on your GameSignal hosting. Hard-refresh the live page. Browse other games’ designs on Websites if you are still choosing a layout.

Related guides

• Rules pages — link appeals to the right roles
• Whitelist pages — who reviews applications
• FAQ · All guides