dylancomas328 downloadsA manuscript editor with integrated StoryLine scene routing, formatted exports, and Antidote Connect support.
Noveler - A StoryLine Expansion, by Dylan Comas, is a desktop Obsidian plugin for writers who want a focused manuscript editor inside their vault while still working with StoryLine projects.
It bundles the Noveler manuscript writer, StoryLine scene routing, formatted exports, and Antidote Connect support into one plugin. Instead of switching between separate bridge plugins and editor views, Noveler gives you a dedicated writing surface with page layout controls, focus writing, formatting tools, StoryLine integration, and export workflows built around long-form fiction.
If Noveler helps your writing workflow, you can support development through PayPal:
.obsidian/plugins/noveler-a-storyline-expansion/ inside your Obsidian vault.Ctrl/Cmd + S.Noveler opens as its own Obsidian view type, separate from the standard Markdown editor. The editor is designed around manuscript writing, so the first screen is the writing workspace rather than a generic note view.
It includes a top formatting toolbar, a manuscript body, a status bar, live word and character counts, and commands that can be run from Obsidian's command palette.
Page mode presents the manuscript as a visual page with configurable paper size, margins, zoom, header/footer sizing, and rulers. It is useful when you want the editor to feel closer to a printable manuscript or book layout.
Page mode supports:
Ctrl/Cmd + Enter.This mode is especially useful when checking line length, page density, chapter headings, scene breaks, and the overall shape of a manuscript before exporting.
Focus mode strips the editor down for drafting. It can center the active writing area, use typewriter behavior, and dim text outside the current line or paragraph.
Focus mode includes:
Use Focus mode when you are generating prose and want fewer layout distractions. Use Page mode when you are reviewing manuscript structure, page flow, or export appearance.
Noveler includes a responsive top toolbar for common writing and formatting actions. The toolbar adapts to narrower panes and keeps core controls available without requiring repeated command palette use.
Toolbar controls include:
Noveler exposes typography controls that matter for long-form writing, not just inline styling. You can tune the body text, headings, paragraph spacing, indentation, and scene-specific style behavior.
Typography features include:
When editing StoryLine Markdown scenes, Noveler can preserve scene-specific typography in frontmatter or in stored plugin settings. That lets a scene keep its visual writing style without forcing every manuscript scene to look identical.
Noveler can automate common manuscript cleanup while you type or save.
Automation options include:
These tools help keep a manuscript clean without sending text outside Obsidian or requiring a separate formatting pass after every session.
The StoryLine bridge routes StoryLine manuscript work through Noveler while keeping StoryLine as the project-management plugin.
Bridge settings include:
StoryLine.When enabled, StoryLine scene clicks, scene opens, manuscript tab navigation, and compatible scene paths can be redirected into Noveler. By default, Noveler reuses one dedicated editor tab; disable One instance limit in Editor settings to keep different scenes open in separate Noveler tabs. The bridge opens Markdown scene files directly inside a project's Scenes folder or in nested organization folders such as Scenes/Act.
Noveler can display visual-only links for StoryLine Characters, Locations, and Items directly in manuscript text. Each category has its own configurable color and bottom-bar visibility toggle. Links recognize entry names and supported nickname or alias fields, including custom Item fields named NICKNAME / ALIAS. Clicking a link opens the corresponding StoryLine entry without adding link markup to the Markdown scene or its exports.
When text is selected in Noveler, the right-click menu provides searchable Character, Location, and Item submenus. Each submenu lists existing Codex entries and includes a creation action. New entries use a confirmation dialog so the StoryLine Name field and generated Markdown filename use the intended full entry name rather than necessarily using the selected text. Choosing an existing Character or Location adds the selection to its newline-separated Nickname / Alias field when it is not already present, then opens the entry for editing. StoryLine views and Noveler's colored links refresh automatically after Codex changes.
This keeps StoryLine responsible for planning, acts, chapters, scene ordering, and project structure, while Noveler handles the writing surface and formatted manuscript output.
Noveler supports direct Markdown export from the standalone manuscript editor and formatted StoryLine manuscript exports through the StoryLine bridge.
Export options include:
Formatted StoryLine exports are written into an Exports folder inside the StoryLine project area. DOCX and ePub packages are generated directly by the plugin. PDF export uses Obsidian desktop's print-to-PDF capability and requires the desktop app.
Noveler includes an Antidote Connect bridge for users who write with Druide Antidote and Connectix.
Antidote features include:
Available commands include:
The Antidote Grammar Checker Integration plugin and Antidote Connectix must be installed and available on the desktop system.
English is embedded in main.js, so Noveler always has a complete offline interface without an additional language file. Non-English translations live in the repository's .lang directory and use locale filenames such as fr-FR.json with this structure:
{
"locale": "fr-FR",
"name": "Francais (France)",
"strings": {
"Save settings": "Enregistrer les parametres"
}
}
The language menu is beside the Noveler heading in Settings. Noveler queries the GitHub .lang directory to populate this menu automatically and excludes en-US.json because English is built in. Available non-English catalogs are downloaded into the installed plugin's .lang cache and updated when their GitHub files change. Previously downloaded languages therefore remain available without an internet connection. Added catalogs and updates to the active catalog are detected periodically, and labels, commands, menus, notices, editor controls, and integration UI update without reloading Obsidian.
To add a translation, commit a valid xx-XX.json catalog to .lang on the repository's main branch. It will appear in installed copies automatically. Missing or unavailable translations fall back to the embedded English source text. Keep placeholders such as {value} and {value2} unchanged in translated values.
Translations should describe each control in its Editor, Settings, or StoryLine context. Keep product names and installed font-family names unchanged.
Noveler stores its settings in the plugin folder and can migrate from earlier Noveler-related plugin setups.
On first load, Noveler can import an existing settings file from:
.obsidian/plugins/noveler/Noveler Settings.json
noveler-a-storyline-expansion plugin folder..obsidian/plugins/noveler-a-storyline-expansion/
manifest.json
main.js
styles.css
1.5.0 or newer.noveler-a-storyline-expansion.Noveler - A StoryLine Expansion is licensed under the MIT License.
Copyright (c) 2026 Dylan Comas.
See LICENSE for the full license text.