Sometimes I think there are two types of writers in this world: those who have discovered Scrivener and those who still write on papyrus. Just kidding; I am no writing snob. I’m definitely attached to my notebook and pen, but there’s no doubt that Scrivener has changed the way I work and write.
I love technical blog posts, especially those that can take you through the entire process of building an app, A to Z. After reading thousands of technical blog posts and writing many myself, I’ve decided that it’s time to share a workflow that I hope will help those who are creating amazing things to blog more easily and often. The specific tools utilized in this workflow are Mac OSX based, but the concepts can be applied to any toolchain. Check
more here - How I Write Technical Blog Posts.
Having traditionally published two books (and being in process with my third), I field a lot of questions from writers about how I manage my book projects, what kinds of software I use, and what my schedule looks like.
Here’s a brief summary of my process:
more here - via How I Use Scrivener To Organize My Book Writing | TODD HENRY.
by Ed Ditto
In 2013 I spent ten days on a writing project that ended up earning $55,000. But I’ll never collect a penny of it…and yet I’m perfectly OK with that. What I wrote was a grant application for a local fire department.
Grantwriting–an application-based process for convincing moneyed individuals and institutions to fund public-good projects–can be an excellent way for writers to use their skills to the betterment of their communities. That’s because it draws on many of the same skills that writing a book does:
- Idea generation
- Careful organization
- Thorough research
- Meticulous planning
- Crafting a compelling narrative
- Conscientious follow-up and administration.
Not surprisingly, I find Scrivener to be an outstanding grantwriting tool. I work with several different charitable organizations and public service agencies, and I keep a separate project for each one, but they all share a common structure and rationale, so I’d like to share those with you.
more here - The best $55,000 I never earned | Good Words.
For almost a year now, I have been using a set of scripts that automatically collect all kinds of statistics and details about my writing, and because of that, I can walk through the the evolution of a story I wrote during that time, from idea to publication. I thought I’d give this a try in order to provide others who are curious about how this writer goes about his craft, a peek behind the scenes.
My production stack, which are the tools used to create my work, is a collection of word processors, text editors, illustration programs, publishing tools, programming environments, and A/V editors. Each application is used to create finished artifacts: graphics, sound files, formatted documents, or working software.
My productivity stack, by comparison, is what helps me manage my knowledge, goals, tasks, timetables, and channels of communication toward the production of those finished artifacts. In some sense, I regard productivity as a necessary evil, which I tolerate because I overload my plate with dozens of personal interests and external commitments; the productivity stack helps me compartmentalizing and track related work, and reminds me what I should be doing to maintain progress and deliver on-time. It helps me choose what to do next by keeping track of every possible task, and it fills the gaps in my memory when it falters. This reduces overall anxiety, and having access to everything keeps me from taking on too much work at one time.
I’ve annotated yesterday’s list of productivity tools with their function:
I’ve just discovered Scrivener, and it’s changing my life. I wish I had found it sooner. The workflow is designed especially for writers, whether you’re writing a novel, short story, screenplay or research paper, it’s easy to organize your scenes and notes. At the moment, there is no iOS app, but it will sync with various text editing apps, including WriteRoom. Now I use WriteRoom on my phone or iPad when I’m out and about, and return to Scrivener on my laptop when I’m home.
Below are some workflows between my typical writing apps, using Markdown as a writing syntax. I can use Markdown to format my notes and texts quickly ready for publishing to my blog, through Scrivener, and even into my huge research and notes database in Evernote.
Over the past few months, I’ve had several people ask me about the tools I use to put papers together. I maintain a page of resources somewhat grandiosely headed “Writing and Presenting Social Science”. Really it just makes public some configuration files and templates for my text editor and related tools. Things have changed a little recently—which led to people asking the questions—so I will try to lay out the current setup here. I will also try to avoid veering off into generalized noodling about the nature of writing or creativity. (That’s fine for Merlin.) This is mostly because although I am not a bad writer, I am an excellent procrastinator, and it is embarrassing to write about how to write papers when you could be actually writing papers. My excuse today is that I have a headcold.
So, first I will say a little bit about the general problem, and then I will tell you something specific: how to take the draft of a scholarly paper, typically including bibliographical references, figures, and the results of some data analysis, and turn it into nice-looking PDF and HTML output. The hopefully redeeming thing about this discussion is that it will help you use the various resources I make available for doing this. If you want to copy what I do, you should be able to. But I am not saying you ought to. Nor am I making any claim that what I do is right, rational, efficient, productive, or psychologically healthy. As in an earlier discussion of mine on this topic, my chief counterexample to taking anything here as advice about writing or productivity is my wife, who—as I type this—is seated opposite me at the dining room table, putting the final touches to a book written in Microsoft Word. I think MS Word is unpleasant to use for all kinds of reasons, and perhaps you agree. The fact remains she just used it to write a book that will be published later this year by Oxford University Press. On this side of the table, meanwhile, I have this blog post.
more here - Plain Text, Papers, Pandoc – Kieran Healy.
Here, in case it’s of any interest is what a Scrivener project looks like for me when it’s heading into the final straight. And below this very large screenshot I’ve pulled out the important component parts.