Add a collection

A set of events that share a property — women in independence, founding moments, rebellions. Cheap to author; the events do the work.

Collection vs. thread

Collections are sets. No per-member notes, no transitions. Members appear in chronological order automatically. Use this when the gathering is the point.
Threads are sequences. Every step gets a note and a transition. Use a thread when you want to make an argument, not just surface a kinship.
Two ways to add members. Pick events explicitly (good for small, deliberate sets) or use a tag selector (good for sets the corpus already knows about — every event with that tag joins automatically).
Tags are free-form. If your collection wants a tag that doesn't exist yet, invent it and add it to the relevant events via the event form first.

1. Collection metadata

Title *

The kinship in a phrase. e.g. "Women in the independence movement"

ID * kebab-case, auto-suggested

Subtitle italic line under the title

Summary * 30–80 words

The elevator pitch. Shown in the picker before the reader opens.

0 words

Framing optional, ≤200 words

An editorial paragraph above the member list. Use this when the framing matters more than the gathering itself — to argue why the collection deserves surfacing.

0 words

Verified? *

2. Build the membership

Add members two ways: pick an event explicitly, or write a tag selector that grabs every event with that tag.

Search the events corpus

Loading the events corpus…

Members

3. Sources optional

Where the editorial framing comes from. Strongly recommended when the collection makes a non-obvious argument.

Validation

Fill in the form above; errors will appear here as you build the collection.

Preview

// fill in the form to see the preview

Submit your contribution

Download saves the JSON to your computer. Pull request opens GitHub's web editor with the file pre-populated. Issue opens a GitHub issue with the JSON in the body.