<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SearchIndexes Version="1.0">
    <Documents>
        <Document ID="54">
            <Title>Notes</Title>
            <Synopsis>Notes and research located here</Synopsis>
        </Document>
        <Document ID="106">
            <Title>Logo</Title>
            <Text>



(your logo)</Text>
        </Document>
        <Document ID="113">
            <Title>Blank Page</Title>
            <Text>&lt;$BLANK_PAGE&gt;</Text>
            <Notes>During Compile, Scrivener will try to remove any unnecessary blank pages. The &lt;$BLANK_PAGE&gt; tag tells Scrivener to leave this page blank (the tag itself will be removed from the compiled document).</Notes>
        </Document>
        <Document ID="120">
            <Title>Keywords</Title>
            <Synopsis>List of keywords needed for Amazon (or other distributor). Amazon has a limit of 6.</Synopsis>
            <Text>Scifi fantasy action adventure
Space opera colonization thriller
Super awesome great story that rocks
Do your research
Give it some thought
Romance</Text>
        </Document>
        <Document ID="121">
            <Title>About the Author</Title>
        </Document>
        <Document ID="107">
            <Title>Blank Page</Title>
            <Text>&lt;$BLANK_PAGE&gt;</Text>
            <Notes>During Compile, Scrivener will try to remove any unnecessary blank pages. The &lt;$BLANK_PAGE&gt; tag tells Scrivener to leave this page blank (the tag itself will be removed from the compiled document).</Notes>
        </Document>
        <Document ID="49">
            <Title>Cover</Title>
        </Document>
        <Document ID="114">
            <Title>Ebook</Title>
        </Document>
        <Document ID="108">
            <Title>Title Page</Title>
            <Synopsis>Title page to the manuscript.</Synopsis>
            <Text>

Book Title







SERIES TITLE

—

BOOK ONE</Text>
            <Notes>This is the title page of the manuscript. Note that “Compile As-Is” is ticked - this ensures that the title page’s formatting doesn’t get changed during the Compile process, even though the formatting of other text documents will be overridden to use a standard 12-point manuscript font.

The &lt;$PROJECTTITLE&gt; and &lt;$fullname&gt; tags get replaced with the information set in Project &gt; Meta-Data Settings… &gt; Project Properties. You can edit those settings or just replace this text altogether. (Other information is taken from Address Book when the project is created.)</Notes>
        </Document>
        <Document ID="115">
            <Title>Logo</Title>
            <Text>



(your logo)</Text>
        </Document>
        <Document ID="0">
            <Title>Manuscript</Title>
        </Document>
        <Document ID="80">
            <Title>Theme</Title>
            <Synopsis>Yes, it’s like putting smoke into a bottle, but it can be done. Not to be confused with concept, theme is what your story is illuminating about real life.</Synopsis>
            <Notes>Source: http://www.writersdigest.com/tip-of-the-day/spotlight-on-story-engineering-the-six-core-competencies</Notes>
        </Document>
        <Document ID="116">
            <Title>Title Page</Title>
            <Synopsis>Title page to the manuscript.</Synopsis>
            <Text>

Book Title







SERIES TITLE

—

BOOK ONE</Text>
            <Notes>This is the title page of the manuscript. Note that “Compile As-Is” is ticked - this ensures that the title page’s formatting doesn’t get changed during the Compile process, even though the formatting of other text documents will be overridden to use a standard 12-point manuscript font.

The &lt;$PROJECTTITLE&gt; and &lt;$fullname&gt; tags get replaced with the information set in Project &gt; Meta-Data Settings… &gt; Project Properties. You can edit those settings or just replace this text altogether. (Other information is taken from Address Book when the project is created.)</Notes>
        </Document>
        <Document ID="123">
            <Title>Leave a Review</Title>
            <Text>Leave a Review

Thanks for reading Book Title! Your support makes it possible for this independent author to continue creating.

If you liked what you read, please leave an honest review wherever you bought this book! Your feedback is invaluable.</Text>
        </Document>
        <Document ID="81">
            <Title>Structure</Title>
            <Synopsis>What comes first, what comes next, and so forth…and why. And no, you can’t just make it up for yourself. There are expectations and standards here. Knowing what they are is the first step toward getting published.</Synopsis>
            <Notes>Source: http://www.writersdigest.com/tip-of-the-day/spotlight-on-story-engineering-the-six-core-competencies</Notes>
        </Document>
        <Document ID="109">
            <Title>Copyright</Title>
            <Text>Copyright

This is a work of fiction. Names, characters, places, and incidents are the product of the author’s imagination or are used fictitiously. Any resemblance to actual events, locales, or persons, living or dead, is entirely coincidental.

Book Title

Copyright © 2015 by Author Name
Edited by Editor Name
Cover design by Designer Name

All rights reserved.</Text>
        </Document>
        <Document ID="82">
            <Title>Scene Execution</Title>
            <Synopsis>You can know the game, but if you can’t play it well you can’t win. A story is a series of scenes with some connective tissue in place. And there are principles and guidelines to make them work.</Synopsis>
            <Notes>Source: http://www.writersdigest.com/tip-of-the-day/spotlight-on-story-engineering-the-six-core-competencies</Notes>
        </Document>
        <Document ID="117">
            <Title>Copyright</Title>
            <Text>

Copyright

This is a work of fiction. Names, characters, places, and incidents are the product of the author’s imagination or are used fictitiously. Any resemblance to actual events, locales, or persons, living or dead, is entirely coincidental.

Book Title

Copyright © 2015 by Author Name
Edited by Editor Name
Cover design by Designer Name

All rights reserved.</Text>
        </Document>
        <Document ID="124">
            <Title>Newsletter</Title>
            <Text>Newsletter

A pitch for your newsletter. What do they get for free? Why should they sign up?

Link to your sign up page</Text>
        </Document>
        <Document ID="90">
            <Title>Part Two Exposition (Response)</Title>
            <Synopsis>Whatever his life course and need was before, it’s either put on hold or altered because of a new calling or need, as presented and defined by the First Plot Point.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="83">
            <Title>Writing Voice</Title>
            <Synopsis>The coat of paint, or if you prefer, the suit of clothes, that delivers the story to the reader. The biggest risk here is letting your writing voice get in the way. Less is more. Sparingly clever or sparsely eloquent is even better.</Synopsis>
            <Notes>Source: http://www.writersdigest.com/tip-of-the-day/spotlight-on-story-engineering-the-six-core-competencies</Notes>
        </Document>
        <Document ID="6">
            <Title>Scene Title</Title>
            <Synopsis>A short, poignant description of your scene’s mission and vision.</Synopsis>
        </Document>
        <Document ID="91">
            <Title>Midpoint</Title>
            <Synopsis>New information that enters the story squarely in the middle of it, that changes the contextual experience and understanding of either the reader, the hero, or both.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="118">
            <Title>Newsletter</Title>
            <Text>Newsletter

A pitch for your newsletter. What do they get for free? Why should they sign up?

Link to your sign up page</Text>
        </Document>
        <Document ID="125">
            <Title>About the Author</Title>
            <Text>About the Author

[author photo]

Author bio

Website: authorwebsite.com
Twitter: @twitter
Facebook: facebook.com/authorpage</Text>
        </Document>
        <Document ID="84">
            <Title>Cut Scenes</Title>
        </Document>
        <Document ID="77">
            <Title>Six Core Competencies</Title>
        </Document>
        <Document ID="92">
            <Title>Part Three Exposition (Attack)</Title>
            <Synopsis>Whereas the hero has been reeling and reacting and fleeing and rebounding, at the Midpoint of the story he begins to fight back, to move forward to seek a solution.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="85">
            <Title>Concept</Title>
            <Synopsis>The idea or seed that evolves into a platform for a story. Best and most empowering when expressed as a “what if?” question. The answer leads to further “what if?” questions in a branching and descending hierarchy, and the collective whole of those choices and answers becomes your story.</Synopsis>
            <Notes>Source: http://www.writersdigest.com/tip-of-the-day/spotlight-on-story-engineering-the-six-core-competencies</Notes>
        </Document>
        <Document ID="79">
            <Title>Character</Title>
            <Synopsis>Don’t leave home without one. Every story needs a hero. We don’t need to like them (contrary to what your high school composition teacher told you), but we do need to root for them.</Synopsis>
            <Notes>Source: http://www.writersdigest.com/tip-of-the-day/spotlight-on-story-engineering-the-six-core-competencies</Notes>
        </Document>
        <Document ID="119">
            <Title>Table of Contents</Title>
            <Text>Table of Contents

Chapter 1
Chapter 2
Chapter 3</Text>
        </Document>
        <Document ID="126">
            <Title>Genre</Title>
            <Synopsis>What genre(s) on Amazon (or other distributor) will you choose when your story in published? Do your research.</Synopsis>
        </Document>
        <Document ID="93">
            <Title>Second Plot Point</Title>
            <Synopsis>The final injection of new information into the story, after which no new expository information may enter the story, and which puts a final piece of narrative information in play that gives the hero everything she or he needs to become the primary catalyst in the story’s conclusion.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="87">
            <Title>Hook</Title>
            <Synopsis>The hook isn’t the First Plot Point. Rather, it’s something that grabs the reader very early in the read and makes her want to stick around.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="94">
            <Title>Part Four Exposition (Resolution)</Title>
            <Synopsis>Wherein the hero conquers his inner demons and becomes the catalyst for the resolution of conflict and the meeting of his goal.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="95">
            <Title>Ending</Title>
            <Synopsis>The final resolution scene or sequence.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="88">
            <Title>Part One Exposition (Setup)</Title>
            <Synopsis>Scenes that introduce the hero, the context, and the stakes of the story, all before something huge happens (the First Plot Point) that really ignites the hero’s journey, need, and quest, which is what the story is really all about.</Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="96">
            <Title>Back Cover Blurb</Title>
            <Synopsis>The sales copy that goes on the back cover of your book</Synopsis>
        </Document>
        <Document ID="89">
            <Title>First Plot Point</Title>
            <Synopsis>The First Plot Point is the moment when the story’s primary conflict makes its initial center-stage appearance.  It may be the first full frontal view of it, or it may be the escalation and shifting of something already present.  In either case, nothing about the story is the same from that moment forward.   </Synopsis>
            <Notes>Source: Story Engineering by Larry Brooks</Notes>
        </Document>
        <Document ID="128">
            <Title>Storyboard</Title>
        </Document>
        <Document ID="97">
            <Title>Sales Page Copy</Title>
            <Synopsis>The sales copy that goes in the “Description” part of your Amazon sales page
</Synopsis>
        </Document>
        <Document ID="23">
            <Title>Characters</Title>
        </Document>
        <Document ID="24">
            <Title>Nine Point Outline</Title>
        </Document>
        <Document ID="32">
            <Title>Character</Title>
            <Text>#
FULL NAME

One Sentence Synopsis
This character in a single sentence.

Summary
This is a paragraph summary of your character. Include physical attributes, habits, mannerism. Sketch your character.

Motivations &amp; Goals
What do they want?

Conflict
What makes them human?

Narrative
What happens to them in the story?</Text>
        </Document>
        <Document ID="25">
            <Title>Template Sheets</Title>
        </Document>
        <Document ID="40">
            <Title>Front Matter</Title>
        </Document>
        <Document ID="19">
            <Title>Chapter Title</Title>
        </Document>
        <Document ID="41">
            <Title>Manuscript Format</Title>
        </Document>
        <Document ID="110">
            <Title>Newsletter</Title>
            <Text>Newsletter

A pitch for your newsletter. What do they get for free? Why should they sign up?

Link to your sign up page</Text>
        </Document>
        <Document ID="42">
            <Title>Title Page</Title>
            <Synopsis>Title page to the manuscript.</Synopsis>
            <Text>Your name
Your address



Your phone number
Your email address
&lt;$wc100&gt; words.










&lt;$PROJECTTITLE&gt;

by &lt;$fullname&gt;</Text>
            <Notes>This is the title page of the manuscript. Note that “Compile As-Is” is ticked - this ensures that the title page’s formatting doesn’t get changed during the Compile process, even though the formatting of other text documents will be overridden to use a standard 12-point manuscript font.

The &lt;$PROJECTTITLE&gt; and &lt;$fullname&gt; tags get replaced with the information set in Project &gt; Meta-Data Settings… &gt; Project Properties. You can edit those settings or just replace this text altogether. (Other information is taken from Address Book when the project is created.)</Notes>
        </Document>
        <Document ID="35">
            <Title>Setting</Title>
            <Text>#
SETTING NAME
Role in story
This setting in a single sentence.

Related Characters
Character A, Character B, Character C.

Description
Describe your setting in significant detail.

Weather &amp; Season
Windy, rainy, gloomy, sunny, clear, foggy, humid, altitude, storms? Summer, spring, fall, winter?

Sights, sounds &amp; smells
Use your senses and go there. Sketch out what aspects of your setting are most important to your character, what they look like, smell like, how the characters feel when they see this place.

Details
Anything else important to remember?</Text>
        </Document>
        <Document ID="36">
            <Title>Settings</Title>
        </Document>
        <Document ID="111">
            <Title>Table of Contents</Title>
            <Text>Table of Contents

Chapter 1				1
Chapter 2				10
Chapter 3				20</Text>
        </Document>
        <Document ID="51">
            <Title>Sales Copy</Title>
        </Document>
        <Document ID="105">
            <Title>Paperback Novel (Interior Only)</Title>
        </Document>
        <Document ID="112">
            <Title>Blank Page</Title>
            <Text>&lt;$BLANK_PAGE&gt;</Text>
            <Notes>During Compile, Scrivener will try to remove any unnecessary blank pages. The &lt;$BLANK_PAGE&gt; tag tells Scrivener to leave this page blank (the tag itself will be removed from the compiled document).</Notes>
        </Document>
    </Documents>
</SearchIndexes>