I use MS Word to author nearly everything I write:
- Workbooks (for courses)
- Blog posts
- Actual real books (Work In Progress)
Much of what it does is pretty good (visual editing, comments from editors, track changes, etc). There are just two things that are slowly pushing me away - books should be reusable parts (quasi OO) and when someone else makes a change I should always know who it is at a glance.
The two big challenges - my workshop materials are made up of parts that can be mixed for different situations and clients. As stands now if we make a change to a section like "Definition of 'Done'" or "User Stories" that have been used in multiple places we either have to update them all or just declare most orphans. I'm writing blog posts for a series Scrum By Example (
https://agilepainrelief.com/notesfromatooluser/2018/08/scrum-by-example.html) and eventually, this will likely become a book - about the unluckiest ScrumMaster ever.
I had hoped one day to find a magical binding tool - where I just created a shell document, wrote a series of include statements and watched a book appear from these parts. I realize that was probably naive at best.
I've surveyed of the playing field as best I can tell. I'm hoping that my peers and friends can tell - if I've missed anything; and what they have used themselves.
Detailed needs (beyond the object idea):
Collaboration is possible - I do the writing but also have an editing team - sometimes we make 2-3 sets of changes in a day
Can see who made which change - one of my editors has a deeper understanding of Agile than the other, it is easier to accept changes from that one rapidly
Can write comments that aren't just in the body of the work - especially from editing team
Features we use from MS Word: footnotes, tables, multi-column text, borders on text, page break, even/odd page breaks, lots of embedded images, headings, footers, links, table of contents, occasionally embed PDFs
Tools I've looked at:
MS Word - missing support for objects
Scrivener -
Pro Does understand that files are objects. It does understand you can rearrange files into parts.
Con UI and Usability from hell. (3.0 might improve that) More importantly its not designed for collaboration. It has an internal versioning system, which is effectively just saving zip files. Others have used it with Github:
https://github.com/carsomyr/scrivener_starter - but that isn't by design - in addition they're saved as RTF files so no joy in using GIT for diff tools. At best the built-in collaboration is import and merge.
LaTeX - Pro Files are objects; Documents are just text files and so the full value of version control is brought to bear. Con: compile times can get large as documents become big. You have to play lots of games to find themes
This book: Better Books with LaTeX - Clemens Lode - outlines how to use to LaTeX publish a book. Editing can either be via a multitude of open source tools
--
What are you using for book authoring, workbooks et al?
Cheers
Mark