0.8.0 — The writer

The writer is a fourth level above the sentence, the story and the vault: what the author is made of, and which stories they are carrying. This release ships the board and its protocol. Nothing on the page changes.

The board

• Open writer (command, the dashboard ribbon icon, or opening Writer.writer) shows every note tagged #writer/<group> as a card inside the groups of a framework, layers stacked down the board: Truby's wish list, premises, inspirations, references and voices by default, or a Generic set, or one written into the writer file. Every group is drawn, with a hint while it is empty. A note in several groups is drawn once, with a chip per group; zoom in and cards show their first lines; lines join cards whose notes link.
• Pan, zoom, Fit; drag cards, move groups with their cards, resize groups from the corner. Drop a card into another group and its tag follows, in the front matter or inline, whichever the note uses.
• Click a group and the board zooms to it; click again, click away or press Escape and the board comes back. The keyboard: arrows move between groups and lanes (the stories band is the lane above the first layer), Shift+arrows between the cards of a group, Alt+←/→ carry a card into the neighbouring group with its tag, PgUp/PgDn and 1–9 jump lanes, Enter on a group opens the new-note form (Enter creates and stays, Ctrl+Enter creates and opens), Enter on a card opens the note, Delete takes a card out of its group, f fits, z fits the selection, / finds, p folds the panel, ? lists them all. Tab is never taken and Ctrl/Cmd stay with Obsidian; the moves are commands too, so they can be rebound.
• The panel: framework, search, a group for new cards, Add note… (a picker over the vault), New note… (a tagged note, created where Obsidian puts new notes), colours per group, layers to hide, the tag prefix. A card's side panel opens the note, removes it from a group, adds it to another, and lists the cards it links to.
• Layout, colours and the view go to one Writer.writer file, found by extension, created in the stories folder on first save. Obsidian Sync carries it with Sync all other types on; the docs say so first.
• The board follows the vault: a tag added by hand appears on the next metadata pass, a renamed note keeps its place.

The stories band

• Every declared project sits above the layers as a story card: name, stage, premise, and one line with words against the target, the cast and the last day the log saw it change. The side card sets the stage (writing-stage, or inferred from prose and the target), opens the map, timeline, threads, manuscript and desk for that project, and links to the idea it grew from.
• Idea pills are premise cards with no story yet; Make this a story… scaffolds a folder (or copies one marked story-template: true, with {{name}} replaced), writes story: true, the stage, the premise and writing-idea into the project note, and writer-story into the idea, which stays where it is. New story… in the panel starts from nothing.
• Unfiled pills are folders under the stories folder with prose and no declaration; Declare a story writes story: true into the folder's namesake or first note.

Uses and lines

• A story uses a card when a note in its folder links to it, by wikilink or by a %% REF: [[Card]] %% comment. Reference a writer card drops one at the cursor from a picker; REF is now a built-in comment tag. Cards show how many stories use them, a card in two or more is marked recurring, a card's side card lists the stories, a story's lists what it draws on.
• Named lines. Click a line between linked cards, or Name… beside a link, and give it a name and a colour; a pair may carry several. Names live in the writer file and go dashed when the notes stop linking.
• A test pins the privacy rule: a REF comment never reaches the prose a model reading is built from.

Voices, fingerprints, reading

• A story adopts a voice (a card in the Voices group) from its side card, written as writing-voice; the voice's side card lists its adopters.
• Every story with prose shows a fingerprint: reading ease, grade, sentence variety and dialogue share over its prose notes. A voice card blends the fingerprints of the stories that adopted it, so the voice on the page can be checked against the voice on the card.
• Reading cards carry reading: to-read | reading | read, set from the side card, shown as a chip; a linked craft note is offered as the analysis.
• The myth report's archetypes gain Add to writer: a REF to an existing archetype card, or a new tagged archetype note with the evidence.

The protocol

• Copy writer schema puts the writer protocol on the clipboard for your vault's framework and tag prefix: which #writer/<group> tags make a note a card, the project-note keys, the %% REF: [[Card]] %% comment, and the Writer.writer file format. Paste it to a person or a tool migrating a board into the vault; the plugin ships no importer on purpose.
• Two frameworks, both macro rather than per-story: Truby (wish list, premises, inspirations, references, voices) and Generic. Your own can be written into the writer file.
• Settings → Writer → Stories folder: where ideas are scaffolded, new cards go and the writer file is created.
• The domain for the board (frameworks, tags, the writer file, the board, uses) is in place and tested; the view follows in the next phase.