Story Editor Tools
Overview
The Story Editor is the primary tool for writing and editing content in Rundown2. It appears on the right side of the screen when you select a story from your rundown list.
Formatting and Text Editing
Basic Text Formatting
-
Bold (B): Bold text
-
Italic (I): Italic text
-
Underline (U): Underlined text
Headings
-
H1: Large heading
-
H2: Medium heading
-
H3: Small heading
-
P: Normal paragraph
Lists
-
Bullet list: Bulleted list
-
Numbered list: Numbered list
Cleaning Tools
-
Clean: Removes all formatting from selected text
-
Remark: Converts selected text into a remark (a visually highlighted comment or note inside the manuscript)
Pagebreaks
Pagebreak tools control where page breaks occur when exporting to PDF:
-
NewPage: Inserts a page break in both A4 and A5 formats
-
A4_NewPage: Inserts a page break only for A4 format
-
A5_NewPage: Inserts a page break only for A5 format
These are typically used for cuecards or scripts when you want to control where new pages begin.
Production Notes
Sidenote
Creates a production sidenote displayed in the margin next to the text. Useful for instructions, crew notes, and production details that should not appear in prompter text.
Function (Asset Package only)
A special type of sidenote for function descriptions or technical notes tied to assets.
Production Tags
Tags that mark technical production elements:
-
Input: Camera settings and input sources
-
Video: Video playout from server
-
Graphic: Graphic elements
-
Sound: Sound effects and music
-
Light: Lighting instructions
-
Props: Props and set elements
-
Instruction: General production instructions
All tags can be linked to assets if an Asset Package is enabled.
View Settings
At the top of the editor you can toggle visibility of different elements:
-
Items: Show or hide production tags (CAM, VIDEO, etc.)
-
Sidenotes: Show or hide production notes in the margin
-
Remarks: Show or hide remark text (comments inside the manuscript)
When a category is hidden, the related button changes appearance to indicate it is disabled.
Top Bar Features
Story Title
-
Click the story title to rename it
Comments
-
Comment button with a badge showing the number of comments
-
Opens the comment panel for that story
-
Used for team feedback and discussion on specific stories
Version History
-
Time Machine icon to view previous versions of the story
-
Restore earlier versions if needed
Delete Story
-
Trash icon to delete the story
-
Deleted stories can be recovered in Deleted Stories if the History module is enabled
Locking System
The editor uses a locking system to prevent multiple users from editing the same content at the same time:
-
Content lock indicator appears when someone is editing
-
If another user holds the lock, you can see who has it
-
You can force-take the lock if necessary, but this may overwrite another user’s work
Keyboard Shortcuts
-
Ctrl + F10: Save content immediately
-
Esc: Close dropdown menus (for example the pagebreak menu)
Automatic Saving
The editor automatically saves your work:
-
Saves about 2 seconds after you stop typing
-
Saves when you leave the editor
-
Shows a Last edit timestamp at the bottom
Mobile Mode
On mobile devices:
-
A Back button appears at the top to return to the story list
-
Layout is optimized for small screens
-
Touch-friendly interface
Asset Integration
If an Asset Package is enabled:
-
Click INPUT, VIDEO, or GRAPHIC items to open the asset menu
-
Add, edit, or remove assets linked to tags
-
Linked assets are displayed visually inside the tag
Special Features
Remark Lines
Text marked as a Remark uses special formatting:
-
Visually highlighted in the editor
-
Can be shown or hidden with a toggle
-
Typically excluded from prompter export depending on settings
Sidenotes with Connector Lines
Production sidenotes appear in the margin with connector lines to the relevant text, making it easy for crew to see what the note refers to.
Read-Only Mode
Used for viewing previous versions or deleted stories without allowing edits.
Tips and Tricks
-
Use Remarks for notes that should be visible in the script but not in the prompter
-
Use Sidenotes for technical instructions and crew notes
-
Use page breaks strategically to control printed output
-
Use tags to make technical elements easy to spot during production
-
Use comments for feedback and team discussion
-
Use Version History as a safety net if something goes wrong