Become a Grok Scribe

Grok Scribes are attendees who help capture the collective knowledge of the conference — session notes, photos, key quotes, discussion summaries, resource links. This repo is the living record of Grok '26, and scribes make it richer for everyone.

If you like taking notes, snapping photos, or just want a reason to pay closer attention, this is for you.

Tip: Share the link to this page with your favorite AI assistant or coding agent — it has everything it needs to help you get set up and start contributing.

Getting Access

1. Email [email protected] with the subject line "Grok Scribe" and include your GitHub username.
2. You'll be added as a collaborator on the grok-26 repository.
3. Clone the repo:

   git clone https://github.com/fellowhumans/grok-26.git
   

4. Use any text editor — VS Code, Cursor, or even GitHub's web editor all work great.

Contributing via Pull Request

All scribe contributions go through pull requests so changes can be reviewed before they go live.

Command line:

1. Create a branch for your changes:

   git checkout -b scribe/your-name
   

2. Make your edits, then commit with a clear message:

   git add .
   git commit -m "Add notes for Peter Barth keynote"
   

3. Push your branch and open a pull request:

   git push -u origin scribe/your-name
   

   Then follow the link in the terminal to create a PR on GitHub, or go to the repo page and click "Compare & pull request."

GitHub web editor (easiest if you're new to git):

1. Navigate to any file on github.com and click the pencil icon to edit.
2. When you save, GitHub will automatically create a branch and open a pull request for you — just give it a clear title like "Add notes for Peter Barth keynote."

Either way, someone from the Grok team will review and merge your PR.

What to Capture

Keynote & Talk Notes

The .talk.md files currently have a short speaker bio and topic summary. Add your notes below the existing content — key takeaways, memorable quotes, themes, links to things the speaker referenced.

Where: paths/01-thu/keynote-1.talk.md, paths/02-fri/keynote-1.talk.md, etc.

Example — before:

# Keynote: Peter Barth

Peter Barth has worked across tech from almost every angle...

At Grok, Peter talks about standing out in a world that keeps moving the goalposts.

Example — after:

# Keynote: Peter Barth

Peter Barth has worked across tech from almost every angle...

At Grok, Peter talks about standing out in a world that keeps moving the goalposts.

---

## Notes

- Opened with the story of launching The Iron Yard out of a coworking space in Greenville
- Key theme: differentiation isn't about being louder, it's about being more specific
- "The people who stand out aren't trying to — they're just solving a problem nobody else noticed."
- Referenced the concept of "taste" as a competitive advantage in product work
- Q&A touched on how AI changes the calculus for early-stage founders

10/20 Session Notes

The group files (*.group-N.10-20.md) are currently stubs with just a room assignment. This is where scribes can add the most value — document what actually happened.

Where: paths/01-thu/10-20s/thu-1100.group-1.10-20.md, etc.

What to capture for each presenter:

• Presenter name (link to their badge if possible: [Name](/../people/slug/slug.badge.md))
• Topic title
• Summary of the talk or discussion (3-5 bullets)
• Key takeaways or resources shared

Photos

Add photos to a photos/ folder within the relevant day directory. Reference them from session files using relative markdown image links.

Where: paths/01-thu/photos/, paths/02-fri/photos/

Naming convention: Keep filenames descriptive and lowercase:

• keynote-1-peter-barth.jpg
• thu-1100-group-1-whiteboard.jpg
• evening-drinks-fireforge.jpg

Adding a photo to a session file:

![Peter Barth on stage](/photos/keynote-1-peter-barth.jpg)

Keep files at reasonable resolution — no enormous raw camera files.

Location Tips

The .location.md files describe venues and restaurants. Add your own tips, reviews, or recommendations.

Where: paths/locations/gvl-lunch-spots.location.md, paths/locations/fireforge.location.md, etc.

General Observations

If something doesn't fit neatly into a session file, you can add it to the relevant day's beat files (kickoff, wrap-up) or start a discussion with other scribes about where it belongs.

File Conventions

All content lives under paths/. Files use a name.type.md naming pattern:

Directory structure

paths/
├── index.path.md          ← main schedule
├── 00-wed/                ← Day 0 (Wednesday)
├── 01-thu/                ← Day 1 (Thursday)
│   ├── keynote-1.talk.md
│   ├── 10-20s/
│   │   ├── thu-1100.10-20.md
│   │   ├── thu-1100.group-1.10-20.md
│   │   └── ...
│   └── photos/            ← add photos here
├── 02-fri/                ← Day 2 (Friday)
├── locations/             ← venue & restaurant info
├── people/                ← attendee badges
└── shared/                ← guides, FAQ, this doc

Guidelines

• Add, don't replace. When in doubt, add content below what's already there.
• Keep it concise. Bullet points over paragraphs. Future readers will thank you.
• Attribute ideas. Quote speakers by name, link to their badge when possible.
• Don't touch the plumbing. Leave YAML front matter (the --- blocks at the top of files) and HTML comments like <!-- id: ... --> alone — these are structural.
• Don't rename or move files. The schedule links depend on exact file paths.
• One topic per commit. Makes it easier to review and merge.
• Follow the Code of Conduct.

Questions?

Find any member of the Grok team at the conference, or email [email protected].