Here is another helpful post from the Archer’s Aim blog on elements for your Scrivener document template.
A few weeks ago, I shared about using the document template feature of Scrivener. It allows you to create a template internal to your project with differing features and content so you can start writing more quickly without forgetting your commonly used elements for your documents. It makes the process of writing approachable.
But what should you include in a document template? How much should you include? What’s the benefit of this bit of work? Let’s take the last two questions first.
As to how much you should put into a document template, this depends on your needs. If you need a simple template with all the common formatting for your project then it’s a straightforward process. If the nature of your project requires more information then you should include that. For instance, with a blog or newsletter project (assuming you are using a year-long project for these), you…
View original post 604 more words