Skip to main content

Build characters, locations, and a story world

Visual cards present readable local files through structured forms. Built-in cards and templates are included with Free. Creating custom templates, properties, relationships, and visual structures requires Pro.

1. Define the smallest useful model​

Begin with the information you will actually search or review:

  • characters: goals, positions, and status;
  • locations: hierarchy, coordinates, and environment;
  • organizations: alignment, members, and resources;
  • events: dates, participants, locations, and outcomes; and
  • other setting material: rules, species, objects, or history.

Do not create a large set of empty fields for completeness. Consistent categories, tags, and relationship names are more useful than a high field count.

2. Create cards from built-in templates​

  1. Select a destination folder or a creation action in Story.
  2. Choose the closest built-in template.
  3. Enter a title and review the category.
  4. Complete the necessary properties, relationships, and content sections.
  5. Save, then open the record once from Project, Search, and Story.

3. Connect records and prose​

Use explicit relationships for stable meanings such as family, membership, conflict, or location. Use ordinary or Wiki-style links to point from prose to a related chapter or card. Canvas connectors belong only to that canvas and do not become card relationships automatically.

Removing a text link does not remove a structured relationship, and the reverse is also true. Before editing, decide whether you mean to change a prose reference, a link in Related Files, or a card relationship.

4. Review completeness through views​

  • Spreadsheet finds missing fields and inconsistent tags.
  • Gallery tests whether titles, summaries, and images are recognizable.
  • Relationship graph checks character and organization networks.
  • Map checks coordinates and spatial relationships.
  • Timeline checks world history and character ages.

5. Use a custom Pro model only when needed​

If built-in templates cannot express a stable requirement, duplicate a template and add the necessary property or relationship. Test it with a few cards before migrating existing metadata. Do not begin by rewriting the entire Project.

For a guided scenario, see Build a fantasy world.