Document

Characters, locations and props each have a Profile view: link a Google Doc about that one asset and the app fills the asset in from it. The project's Document view is the same idea at the scale of the whole show. Write your show up in one document -- what it is, who is in it, where it happens, what turns up in it, and the episodes you have in mind -- point the project at that document, and it offers you everything it found.

Nothing is created until you say so. What the document produces is a list of proposals; you review them, correct anything that is wrong, and accept the parts you want.

Linking the document

The first thing the view asks is where your document lives. The choices are the same as on a Profile page: a Google Doc (the best one -- the app reads its headings and lists as structure and pulls its pictures in too), a Google Drive file, a local file, or writing Markdown in the app.

Save it and the app loads the content. Refresh re-reads it after you have edited the document.

Step 1 -- Read the document

You see the document as the app has read it. When it looks right, click Find sections.

This first pass does one thing: it works out which parts of your document are about what. It looks for the show itself, for each named character, each place, each object and each episode, and notes which stretch of text belongs to which. It does not fill in a single field at this stage -- it is only working out who is who.

Step 2 -- Review what it describes

This is the important step. You get one row per section, in the order they appear in the document, and each row tells you three things you can change:

Control	What it does
This section is about	The kind: the show, a character, a location, a prop, or an episode. Change it if a place has been read as an object.
Name	The name that will be used. The show's own row takes its name from the project.
Goes to	Whether to create something new, use something you already have, or skip this section entirely.

Each row also shows the lines it covers, how many of the document's pictures fall inside it, and a fold-out of the exact text that will be used -- so you can check a section really is about who it claims before anything is made from it.

If your project already has a character with that name, the row is pre-set to use that one. This is what stops a second Julie appearing when you re-read the same document after editing it.

When the list looks right, click Apply. Now -- and only now -- anything that needs creating is created, and each section's text is read a second time, this time against the properties of the thing it is about. A character section fills in character properties, an episode section fills in episode properties, the show's section fills in project properties.

Step 3 -- Review property proposals

Every value the document produced arrives here as a proposal, grouped by the entity it belongs to, showing what is there now beside what is suggested. Accept writes it; Reject discards it. One field at a time, exactly as on a Profile page -- nothing is written to an entity behind your back.

If the document says nothing useful about a field, no proposal appears for it. A document that never mentions props simply produces no props; that is a normal outcome, not a failure.

Step 4 -- Place the images

Pictures in the document -- a portrait under each character, a photo of the set -- are already in the project's Media Gallery when the document is loaded, because at that moment nothing yet knows who they belong to. This step files them where they belong: each picture is offered to the entity whose section it sat under, and File this image adds it to that entity's gallery. File all does the lot.

A picture you leave alone stays in the project gallery. Nothing is thrown away, and filing a picture does not remove it from the project's own gallery -- that stays as the document's record of what was in it.

Reading the document again

Edit the document, come back, Refresh, then Find sections again. Sections you have already applied keep the entity they made, so a second reading updates what you have rather than duplicating it.

Where to go next

• Properties -- the project fields a show section fills in
• Characters, Locations, Props -- each has its own Profile view for a document about that one asset
• Episodes -- the episodes a document's episode sections create