Storybook Writing SoftwareWriting Software Storybook
Organize with Storybook Novel Software
By adding the concept that I am writing several books at once (in different genres), which are all non-sequential, you can see why I have difficulty in attracting and retaining critics, and why I had to find a way to follow and present the narratives in their current state of being.
Jumppadto uses tabs for scene files; Springpadto Tracks characters detail, research results and high-level eBook detail (cover art, logistics, story descriptions ); MS Project to follow the location of clues and timelines; Google Meters to follow geographical movements; Pointerest to follow settings and item detail; and MS Word's documents as my chart.
I was looking for a more complete approach that brought me to Storybook. The Storybook is a free open code novel authoring tool for creatives, composers and contributors. From the story to the final story - with Storybook you never loose the big picture. The Storybook will help you keep track of several storylines while you write your work.
Administer all your information such as personalities, places, scenes, properties, tagging and idea in one place. An easy-to-use graphical environment allows you to map your predefined object to each of your sceneries and keep track of your work with easy-to-use charting features. As with many authoring write utilities, this programme aims to be a complete tool that includes both organising and authoring functions.
However, MS Word is the only utility I'm faithful to, so I only use Storybook to organize. I' m now using Storybook to follow the story, sequence, character, place and time line, and to keep a link to the information that other applications process even better (like a custom Google card to show geographical movements).
In addition to the unexpected, Storybook also has three exciting features: strings, tagging and minds. I haven't found a clear string definitions yet, so here's mine: strings are color-coded clusters of things you want to follow at a high visual standard. Specifically, I use them to show me my dialog in a visual way, to illustrate the relationship between story and story (this makes back story dumping really simple to find).
However, the cool thing is to follow behind the curtain information that is important to the storyline, but not specifically made up in the storyline - for example, what non-action figures are doing at the time. Strangely, the value of a tag is apparently infinite, so most applications use it. The storybook is no exeption, but what it has is a two-pronged tagging approach: Tag andtems.
Like I use tagging for localised things like'show vs tell'. For example, if a player shows some kind of attitude, like frown to show disfavor, I mark this point #emotion #frown #disapproval. While I can make sure that each person shows this attitude consequently for a certain emotional, it is also different from other people. Objects can be used to follow objects verbatim (necklace A goes from letter J to letter Y on the third day, then to place K etc.).
I use them instead to highlight cues, subject matter and behavioural changes over the course of the years ("character arcs", mourning phases, etc.). I' m using this part of the programme to collect criticism from critics and betatakers and (!) to follow changes (related to tags). To have somewhere to follow changes (and more to the point, the argument behind the change) is so important because even the smallest modification can have a big impact on the entire script, and the thing would never get done if I went back and made those changes immediately.
I am currently using the open code Storybook and I am very satisfied with it. What do you do to organise and publicize your storyline items?