Most of the authors we work with here at Sulis International use either Ulysses App or Scrivener for their writing. Here is a helpful article about setting Scrivener up to make it easier to compile (export) to final forms for submission. Some excerpts:
A common anxiety I’ve noticed among my Scrivener students and training clients is over whether they have their project set up “right.”
With Scrivener, you can write in one format, and export in another. You can create an ebook, and then turn around and immediately create a PDF without reformatting any text. This flexibility is possible because Scrivener does not present a WYSIWYG¹ interface for exporting your manuscript.
So, I’m going on the record: There is no right or wrong way to set it up. Scrivener flexes for whatever structure makes sense to you and works with your process.
I realize the Compile function is intimidating to most users, and if you want to just choose the Standard Manuscript Format preset, output your manuscript to Word, and work your magic there, go for it. But understanding file types and hierarchy levels—and that compiling is all about applying rules—is the key to understanding Scrivener’s Compile process.
By utilizing folders to create levels in your Binder, you’ll make compiling easier. And who couldn’t use a little more easy?
There are two key things to understand about the Binder. *insert foot stomping here*
1. Files in the Draft folder (aka Manuscript, Screenplay, etc) will be one of three types: text document, file group, or folder. (Images, PDFs, and other non-text type files must be stored outside of the Draft folder.) Here’s an explanation of each.
2. By putting documents inside folders or file groups, you create an outline-like hierarchy within the Binder so that different files are at different levels. Your Draft folder is always level 0, and each indent is another level in the hierarchy.
