Projects

A project is one piece of writing. Each project has a content type that shapes the coaching around it, and you can assign a voice so every stage works toward the same sound.

Content types

When you create a project you pick a content type — Novel, Blog, Screenplay, and eleven others. Each one tailors the setup interview and the coaching to the kind of writing you are doing. The Content types page describes every one of them.

The setup interview

After you name the project and choose a content type, a coach interviews you — chat style — to gather the context that makes the later stages meaningful: your topic, audience, purpose, and any constraints. The questions are tailored to the content type you picked.

The project is created when the interview is done and you confirm.

The project overview

The overview opens with the substance of your project — its cast, its world, its arcs, and the questions still open — drawn from what your setup interview learned, in your own words. Each is shown under a heading for its kind; a project only shows the kinds it actually has, so a sparse project and a full one both look intentional. There is no completeness score to fill: two characters and a place is a complete starting point. A project with nothing yet — one imported, started blank, or created before this — simply shows its documents and the door back to its brief, with no empty placeholders.

Revisiting setup

For some project types you can re-drive the setup interview later from the project settings, to update its context as the work takes shape. You choose how to begin: pick up where you left off — the coach confirms what you have already answered and asks only about gaps or things that have changed — or start fresh from the first question. Each re-drive is a new interview; your earlier ones are kept.

When the interview is done, you see exactly what changed — each answer side by side with what it was before, labelled with the question that produced it. New and changed answers are ticked for you; removals are not. Nothing is saved until you confirm, and a brief field you have edited by hand is never overwritten unless you accept the change. You can also read your past interviews as they were asked and answered.

If a turn fails, your answer is kept and a Retry button appears — click it to send the same answer again rather than retyping it. The credit for a failed turn is returned. If the error shows a reference code, include it when you contact support.

Your progress is saved on this device as you go, so reloading the page or navigating away and back does not lose the interview. When you return to New project with an unfinished setup, a “Resume your setup” option lets you pick up exactly where you left off — your answers and the coaches you were setting up are still there — or discard it and start clean.

Your first document

When a project is ready, Oghmere offers to start its first document for you — a type chosen from what the interview learned, named and described so you can see what it is (for a novel, a Chapter). Accept to open that document in the editor with its brief already seeded from your interview, pick a different type first, or choose “Not now” to land on the project and start whenever you like. This offer appears for some project types; when it does not, creation simply ends on the project as usual.

Importing existing writing

Already have a draft? When you create a project, choose to import instead of starting blank. Upload a .md, .txt, .docx, .pdf, .rtf, or .epub file and Oghmere analyzes it to pre-fill the project — its structure and setup context — so you can review and confirm rather than starting from scratch. An EPUB is split on the book’s own chapters; other formats are split heuristically. Your formatting comes with it — bold, italics and underline, along with paragraph alignment and first-line indents. A PDF has no styles to read, so its headings and lists are rebuilt from how the page was set: text set larger than the body becomes a heading, bulleted lines become a list, and wrapped lines are joined back into paragraphs. You can select several files at once: each file becomes its own document, and Oghmere reads them together to infer one shared voice and brief — useful for bringing in a set of existing posts. On the review screen each file also gets a proposed document type for your project’s content type — a file named for your characters, an outline, or worldbuilding is proposed as that kind rather than as another chapter, and you can confirm or change the type per file before you create the project. A single file is split into chapters instead. When an import produces more than one document, those documents are grouped into a folder and a Binder named for the project — on the review screen you can rename the group or turn grouping off to keep the documents at the project root. There is a total size limit per import; very large manuscripts may need to be brought in a part at a time.

Inside an existing project you can also bring a single file in as a new document: open any New document menu — the button above the document tree, or a folder’s menu — and choose “Import a file…”. Pick a .md, .txt, or .docx and Oghmere creates a document from its contents (in that folder, when you started from one) and opens it.

Story structure

A narrative project can carry a story structure — the target shape the story-arc chart plots your tension against. Pick one in project settings: Three-act, Freytag’s pyramid, the Hero’s journey, the Seven-point structure, or Freeform (no target shape, for discovery writing). Each option describes the arc it expects, so the chart can show a tolerance band — a zone your act two might sit in, never a single number to hit. A project with none set is charted as three-act and labelled “assumed”, so nothing breaks before you choose; the setup interview can propose a match from what you described, but it is only ever assigned when you confirm it.

Managing projects

Settings → Projects lists your projects by state. Archiving hides a project from navigation without deleting anything — unarchive it anytime to bring it back. Deleting a project moves it to a recoverable state for 30 days, during which you can restore it from the same page; after that it is removed permanently.

Archiving & deleting documents

Individual documents have the same protection. From a document’s menu in the project tree, choose Archive to hide it without deleting anything, or Delete to move it to a recoverable state. Archived and deleted documents are listed under Settings → Projects & Documents: unarchive an archived document to bring it back, or restore a deleted one within 30 days. After 30 days a deleted document is removed permanently. Deleting a folder still just moves its documents to the project root — it never deletes them.