---
title: "Team wiki template – Display"
description: "The start page of an internal knowledge base in plain Markdown – what the company does, where each kind of doc lives, how decisions are made, and who to ask."
---

# Team wiki template

The start page of an internal knowledge base in plain Markdown – what the company does, where each kind of doc lives, how decisions are made, and who to ask.

- Format: Markdown
- Detail page: https://display.dev/templates/team-wiki
- Raw template file: https://display.dev/template-sources/team-wiki.md
- One-click anonymous publish (no account): POST the file to https://api.display.dev/v1/public/artifacts as multipart/form-data (`file` field)

## Agent prompt

Write the start page of our team wiki on Display. Fetch https://display.dev/template-sources/team-wiki.md and keep its sections: a TL;DR, what we do, a table of where things live with who can edit each folder, how we decide, and who to ask. Fill it from our current handbook and the folders we really use. Name real owners, not teams.

Publish it with the Display MCP publish tool if connected. Otherwise POST the file to https://api.display.dev/v1/public/artifacts as multipart/form-data (`file` field, optional `name`) – no account needed. You'll get back `previewUrl` (the link to share) and `claimUrl` (one-shot link to take ownership). Reply with both.

## What this template is for

The first page a new person opens. It says what the company does, which
folder holds which kind of doc, and who can edit each folder. A reader finds
the right page in one step instead of asking in chat.

## How teams use it

- **One owner, a review date.** The header names the owner and the last
  review date, so readers can see when the page is out of date.
- **Fix it in place.** A reader who finds a wrong line comments on it or
  edits it. Every version shows who changed it and when.
- **Your agent keeps it current.** Ask your agent to compare the page with
  the folders you really use and to update the table.

## Template source

````markdown
# Fernhill handbook – start here

**Owner:** People Ops · **Last reviewed:** 1 October 2026 · **Readers:** everyone at Fernhill

> **TL;DR:** This Space holds how Fernhill works. Read *Your first week* on day one. If a page here is wrong, comment on the line or edit it. Every page shows who changed it and when.

## What we do

Fernhill makes planning software for garden centres and plant nurseries. We are 64 people in Bristol, Leeds and remote across the UK. Our customers run 1,900 sites.

## Where things live

| Folder | What is in it | Who can edit |
|---|---|---|
| Start here | This page, *Your first week*, the org chart | People Ops |
| How we work | Meeting notes, planning recaps, decision log | Everyone |
| Policies | Expenses, travel, leave, security | People Ops, Finance |
| Teams | One folder for each team's own pages | That team |

## How we decide

1. Write the decision as a doc in the team's folder. Your agent can write the first draft.
2. Share it with the people who must agree. They comment on the lines they question.
3. The owner records the outcome in the *Decision log* with a date.

## Who to ask

- **Payroll, leave, benefits:** Mette K. in People Ops
- **Laptops and accounts:** IT, in the #it-help channel
- **Expenses:** Finance, see the *Expense and travel policy*
- **Anything else:** your manager or your onboarding buddy
````