The Great Big Scrivener Survey

Thanks for filling in the survey! There’s certainly nothing ignorant or wrong about your responses - this is proving to be an interesting learning experience for us (me!), as it exposes some mistaken assumptions on our part. I now realise that I should have added an “I don’t know what this is” checkbox for the features, which would have shown us areas we needed to publicise more or explain better. You live and learn! A great thing about the survey is that it’s led to users such as yourself, who don’t normally post, getting in touch. I’m looking forward to reading all of the comments entered into the survey’s comment boxes. (Oh, and the good news is that “scrivenings” is so fundamental to Scrivener that even if everyone said they didn’t use it, I wouldn’t remove it. :slight_smile: )

Scrivenings is the single feature that drew me to Scrivener. The rest is nice, but scrivenings was transformative.

Came for the scrivenings, stayed for the compiler.

Yep, once I knew what it referred to, I realized I do use it some, especially if when I’m reading over chapters that have sections and when I’m checking cohesion between chapters or sections. :smiley: And yeah, I can totally understand it being hard to name, especially as you wouldn’t want it to be confused with Compile.

I figured you would like the ability to split and reorder then merge more than complier. I’m a simpleton though and only need compiler to get things to RTF. Word does my formatting because… winblows user base at the office.

I’ve written thousands of pages of technical books, whitepapers, and articles in Word over the years of my career as a Microsoft IT SME and consultant. Word’s outline mode actually is decent enough (and has been for years) that you can easily move content around and re-arrange as long as you’re using the proper header structure from the get-go.

However, before that I was a UNIX sysadmin, and thought I never really got deep into troff or TeX, I did get exposed to systems like DocBook that encouraged you to split structure vs. markup. Scrivenings and the compiler really speaks to that bias for me – set up the Binder however you need structurally, set up the Compiler to produce consistent styled output, and Scrivenings to help bridge some of the navigational gap when dealing with a deep structure.