Content Containers & Units

MythTapestry organises your writing into a unified container hierarchy. Containers hold child containers or content units, forming a flexible tree structure.

Container types

The system uses a single unified Container model with behaviour controlled by container type definitions. Three system types are provided:

Books

Traditional narrative containers for your world’s stories.

• A book (root container) contains chapters (child containers)
• Chapters contain content units — individual scenes or sections
• Chapters are ordered by sequence number within the book

Campaigns

For tabletop RPG or game-oriented worlds.

• A campaign (root container) contains sessions (child containers)
• Sessions contain content units — session notes, recaps, and narratives
• Campaigns support a participants feature for tracking players

Encyclopaedia domains

For reference-style knowledge.

• A domain (root container) contains content units directly as articles
• Domains don’t have child containers — articles sit directly inside
• Useful for topics like “Geography”, “History”, “Magic”

Tip

When you create a world, MythTapestry automatically seeds encyclopedia domains based on your genre, wizard answers, and complexity tier. These come pre-populated with article stubs — ready-made starting points you can fill in or delete. See Creating a World for details.

Note

Each container type definition controls which parent and child types are allowed. Books can only contain chapters, campaigns can only contain sessions, and domains hold articles directly.

Container fields

Containers have both system fields and optional custom fields:

Field	Description
Title	Container name
Description	Text description
Sequence number	Order within parent
System fields	Type-specific fields (defined by the container type definition)
Custom fields	User-defined metadata (defined per type)

Content units

A content unit is an individual piece of writing within a container. This is where your actual narrative, notes, or articles live.

Content unit fields

Field	Description
Title	Unit title
Prose content	Rich text content (TipTap JSON format)
Summary	AI-generated or manual summary
Narrative importance	major, minor, or background — helps prioritise content for AI features
Temporal specification	Calendar-aware positioning using your world’s calendar
Narrative time context	Calendar override, time range, and precision for this unit (see below)
Custom fields	Type-specific metadata defined by content type definitions

Narrative importance

The importance field helps the system prioritise content:

• Major — key scenes, pivotal events, important articles
• Minor — supporting content, secondary details
• Background — flavour text, ambient details, background lore

The chatbot and AI features use this to decide how much weight to give each piece of content when answering questions.

Narrative time context

Each content unit can override the world’s default calendar settings. This creates an inheritance chain:

World defaults → Content Unit override → Inline date mark override

The narrative time context panel in the editor sidebar lets you set:

Field	Description
Calendar	Which calendar system to use (defaults to the world’s primary calendar)
Start / End	A time range in absolute days — when this content unit takes place
Precision	Which temporal scale the time range is precise to (e.g. “Year”, “Month”, “Season”)

Tip

If you leave the calendar set to “World default”, the content unit inherits whatever calendar is configured at the world level. You only need to set an override when a particular scene or section uses a different calendar from the rest of the world.

The precision field lists temporal scales from the selected calendar. Setting precision to “Year” means the start/end days are only accurate to the year — the exact month and day are approximate. Leaving it as “Exact (to the day)” means the dates are precise.

The editor

Content units use a full-featured TipTap rich text editor with:

• Text formatting (headings, bold, italic, lists, blockquotes, etc.)
• Entity mentions — type @ to search and link entities inline
• Date mentions — type [[ to insert a formatted date chip from your calendar
• Inline date links — select any text and assign a precise datetime to it (see Inline Temporal Marks)
• AI entity detection — the system highlights potential entity references in your text
• Autosave — your work is saved automatically as you type

Tip

Entity mentions appear as highlighted links in your text. Clicking a confirmed mention opens the entity’s detail page. Date links appear as subtly styled text with a hover tooltip showing the resolved calendar date.

Dual storage

Content units are stored in two places:

• PostgreSQL — full content, metadata, timestamps, and all fields
• Neo4j — entity graph nodes with relationships and references

This dual storage means your writing is fully searchable in the database while also being part of the knowledge graph for relationship queries and graph visualisation.

Creating content

1. Navigate to a container (book, campaign, or domain) in the sidebar
2. Click Create Chapter/Session (for books/campaigns) or create an article directly (for domains)
3. Click into the new content unit to open the editor
4. Start writing — your work autosaves