# Add a new experience

> For Jenks — create a new experience, project, community or education entry that passes validation and appears everywhere.

## Where the file goes

One entry is one Markdown file. The folder depends on its `kind`:

| kind | path |
| --- | --- |
| `experience` | `content/corpus/experiences/<slug>.md` |
| `project` | `content/corpus/projects/<slug>.md` |
| `community` | `content/corpus/community/<slug>.md` |
| `education` | `content/corpus/education/<slug>.md` |

The `slug` is kebab-case and must equal the file name.

## Template

```markdown
---
slug: acme-ai-advisor
kind: experience
title: AI Advisor
org: Acme Pty Ltd
orgUrl: https://acme.example
location: Melbourne
start: 2026-11
end: present
tags: [ai, consulting]
lenses: [ai-transformation-consultant, head-of-ai]
skills: [AI strategy, Governance]
metrics:
  - One short, factual key result with a number where known
summary: One sentence that says what Jenks did and why it mattered.
featured: false
proof:
  - { type: article, title: "Case study", url: "https://acme.example/case-study" }
---

## Overview

The organisation, the situation and Jenks's mandate.

## What Jenks did

- Concrete actions, one per bullet.

## Achievements

- Results with numbers where they are known.

## Why it matters to employers

Why this experience is relevant to the roles Jenks is targeting.
```

## Field rules

- `start` is `YYYY-MM`; `end` is `YYYY-MM` or `present`. Use `period` (for example `"2010 — 2011"`)
  when exact months are not known, and `approx: true` when dates are approximate.
- `tags` must come from: `it`, `engineering`, `ai`, `devrel`, `web3`, `business`, `marketing`,
  `consulting`, `hospitality`, `community`, `creative`.
- `lenses` must come from: `head-of-ai`, `ai-transformation-consultant`, `engineering-manager`,
  `solution-architect`, `system-integrator`, `support-engineer`, `ict-specialist`,
  `developer-advocate`, `developer-evangelist`, `digital-marketer`, `hospitality`.
- `proof` items need a `type` (`article`, `video`, `code`, `talk`, `paper`, `site`) and a `title`;
  `url` must be `http(s)`.
- Projects can set `timeline: true` to appear in the career timeline too.
- Keep official job titles exactly as on LinkedIn.

The full list is in the [data model reference](/agents/docs/reference/data-model) and in
`jenks admin schema`.

## Images

Add a WebP under `web/public/img/jenks/` (the images folder is not writable through the admin API,
so add images through git). Then set:

```yaml
image: /img/jenks/acme-workshop.webp
imageAlt: Jenks running an AI workshop at Acme
```

`imageAlt` is required whenever `image` is set, and the build fails if the image file is missing.

## Publish

```bash
jenks admin validate content/corpus/experiences/acme-ai-advisor.md acme-ai-advisor.md
jenks admin put content/corpus/experiences/acme-ai-advisor.md acme-ai-advisor.md \
  -m "Add Acme AI Advisor" --branch dev
jenks admin deploys
```

Check `https://dev.jenksguo.xyz/career/acme-ai-advisor`, then `jenks admin promote`.

Once published, the entry appears on the career page and its own page, in all seven languages, in
`/llms-full.txt` and `/experience.json`, and in the answers of the Ask Jenks assistant and the MCP
tools.