3 Major Purposes

Explain Compile steps in detail

Almost everything is covered in this example.

Illustrate diverse exports from a single project

Unlike Word or any other word processor I know of, Scrivener can deliver multiple very different products from a single project. This report illustrates that.

Enable me to make decisions about epigraphs

I need to decide the best chapter for each epigraph and find chapters that don’t have one.

You may have other reasons, or you can use the same techniques to create ANY Compile format. You may not need some details, such as prologues and epilogues. If you come to something you don’t need, ignore it.

What the Report Will Look Like

Binder Structure: Job One For Any Project

I have chapters (Section Type = Chapter), an epilogue and prologue (Section Type = Epilogue-Prologue), and epigraphs (Section Type = Epigraph).

Epigraphs are centered in the Editor

I'll Compile them as-is, and they won't need a special section layout.

Chapter folders

Prologue & epilogue section types

For publication, the prologue and epilogue don't have chapter numbers, but chapters do. The difference doesn't matter for this report, but the Binder structure has to support both Compile formats.