Skip to content

Visual Studio

Writing complex fiction means juggling visual references. Character art commissioned or pulled from Pinterest. Maps you drew yourself or downloaded from a worldbuilding toolkit. Mood boards that establish the visual tone of a specific location. Costume studies for a particular era. Weapon references. Architectural sketches. Real-world photographs that inspired a fictional place. All of it usually ends up in a scattered mess across your desktop folders, your Pinterest boards, your screenshot archives, and whatever else, and by the time you need to find a specific image — “what did I have for Nubia’s appearance?” — it’s faster to Google the name of an actor you think looks right than to dig through your own collection. Visual Studio is the module that fixes this. It’s a visual reference manager that keeps your images next to your writing, linked to your Legendry, and organized by project. It’s also a character sheet designer with agent-driven layout generation, which is a completely different feature that happens to live in the same module because both are visual-output tools.

This page covers both pieces.

The Gallery is where images, video, audio, and document references live. It has upload tools, folder organization, multiple view modes, a mood board canvas, and tight integration with your Legendry for linking visual assets to lore entries.

Four ways to get files into the Gallery:

  • Drag and drop. Drop files anywhere on the gallery surface to upload. The fastest workflow for small batches.
  • File picker. Click the upload button and select individual files through the standard file dialog.
  • Folder upload. Upload an entire folder with a recursive option for subfolders. Useful for bringing in an existing reference collection all at once.
  • Bulk upload. Multiple files in a single operation.

Supports images (JPG, PNG, GIF, WebP, SVG), video, audio, and documents. The 20 MB per-file size limit is configurable in settings.

Visual Studio has its own project concept that lives alongside your writing projects. A project in Visual Studio is a named container with a description, status, tags, and a thumbnail. Switching projects loads a different set of assets.

Most authors use one Visual Studio project per book, matching the structure of their writing projects. Keeping them aligned means the visual references for Book One are separate from Book Two, and you’re not scrolling through mixed asset sets.

Each project can have a nested folder tree for organization:

  • Create folders within a project, with optional nesting to any depth.
  • Folder tree in a collapsible sidebar with asset counts visible per folder.
  • Move assets between folders via drag and drop or the context menu.
  • Move folders under different parents to reorganize.
  • Folder types — general, reference, character, location, object, concept. The type is purely organizational; it doesn’t affect behavior.

Three view modes for looking at your assets:

  • Grid view. Thumbnail cards. The default. Best for visual browsing.
  • List view. Compact rows with filenames and metadata. Best for quick scanning when you know the name.
  • Mood Board view. A free-form canvas. Covered in its own section below.

Filters and sorts:

  • Type filters — All, Images, Video, Audio, Documents, Other.
  • Sort modes — Newest first, Oldest first, Name (alphabetical).
  • Semantic search across asset names, descriptions, and tags. Type a query and the list narrows to matches by meaning, not just keyword.
  • Folder scoping — click a folder in the tree to show only its contents and descendants.

Select an asset to open the detail drawer:

  • Name — editable inline.
  • Description — editable text field. Use for context, attribution, or whatever notes matter.
  • Tags — add and remove inline.
  • Entity links — link assets to lore entries (characters, locations, etc.) with a label. This is the killer feature — it’s how an image on Kent Musa’s Legendry entry gets there.
  • File metadata — type, dimensions, creation date, project.

Double-click any asset (or click once and pick “View”) to open the lightbox:

  • Zoom and pan. Mouse wheel zooms; drag pans. Full gesture support.
  • Navigation. Left and right arrows browse the current filtered set.
  • Info toggle. Show or hide the metadata overlay over the image.
  • Media support. Images render directly; video and audio show player controls.

Mood Board view lays assets out on a free-form canvas instead of a grid:

  • Drag cards to position asset cards anywhere on the canvas.
  • Pan and zoom — middle-click and drag to scroll, mouse wheel to zoom.
  • Bring to front — dragging a card raises it above others in the stack order.
  • Auto-layout. New assets that don’t have an assigned position get arranged in a grid.
  • Persistent layout. Card positions and viewport state save automatically and restore when you come back.
  • Click any card to open its lightbox view.

Mood boards are saved as part of the project. You can have multiple projects with different mood boards, and the layouts persist across sessions.

Toggle bulk selection mode to select multiple assets:

  • Bulk delete and bulk move to a target folder.
  • Clear selection to exit bulk mode.

Useful for large cleanup passes when you’re reorganizing an inherited collection.

Section titled “Where Gallery fits with the rest of Ishvana”

A few integrations worth knowing:

  • Legendry entries can link to Gallery assets. A character entry gets a visual assets section that shows any images linked to that character. Open the character, see their portrait immediately.
  • Bookmaker can pull Gallery assets into compiled books — chapter start images, full-page illustrations, inline figures. The Bookmaker’s image picker reads from the Visual Studio Gallery.
  • Maps are a separate module but visually adjacent — map images can be stored in the Gallery and referenced from lore entries.