Lists & steps

List types

Ordered sequence — steps have meaningful order (1..N): deploy runbooks, recipes, itineraries, learning roadmaps, rankings.
Set / checklist — order doesn't matter: packing lists, review checklists, curated collections.

You pick the type at creation and can change it in the list settings.

Addressing

Every list lives under its owner, GitHub-style:

https://setfork.com/{owner}/{slug}

Slugs are unique per owner. Lists can be public (visible to everyone) or private (owner only); switching visibility is in the danger zone of list settings.

Steps

A step is more than a line of text:

Title — imperative and short ("Back up the database").
Description — the useful details: amounts, temperatures, flags.
Command — one terminal command, rendered with a copy button.
Sub-tasks — checkable sub-items; in runs each can be ticked individually.
Level — required (default), recommended or optional, like MUST / SHOULD / MAY in RFCs.
Why — rationale for non-obvious steps.
Section — a group heading that visually splits long lists ("Day 1", "Dough", "Week 3").
References — labeled links to docs or sources.
Screenshot — drag-and-drop an image onto a step in the editor.

A run is an executable instance of a list pinned to a specific version. Start a run and you get a live checklist: step states (todo / current / done / blocked), per-step notes and sub-task ticks. Runs survive new versions of the list — they stay on the version they started from.

Topics and tags

Every public list can belong to a topic (the colored categories in Explore) and carries free-form tags used by search and discovery. Tags are in English.

Export

Any list can be downloaded as Markdown or HTML, or printed to PDF (steps never break across pages).