Using Binder to recreate MS Word document with reused subdocuments

[Vincent_Vincent]

Hi

@tearaway

Can I maintain all nine works in one project? […]

Yes. But it might become overwhelming. If your work is already done, if you don’t have a good reason to do so editing-wise, perhaps it’d be best to opt for multiple projects instead.
The question requires consideration, but only you can do that.
On the other hand, note that it is far easier to split a project into multiple smaller ones than to assemble small projects into a big one. So, in your case, I’d start with one project containing all 9 books, and if it feels wrong, split it. (You could then duplicate the project first, to retain the “all in one” version and go back to it later on if need be – once you’ve measured the implications.)

@tearaway

[…] Or, what is the best way for coherent management of all nine works having shared content.

There is a placeholder <$include> for that at compile. This way you can edit only one document and all occurrences of that content/document will come out of compile the same (edits and all).
Check out this post of mine about mirroring documents in the binder. [The whole thread is worth it.] (Because no, Scrivener otherwise doesn’t per se allow it.) :

Replicants: the ability to file a document in several places

You could create a blank document where in the binder you’d otherwise have placed the replicant. Name it “Yourdocument_replicant” or something like that. Add the document you wish be replicated in this new document’s document bookmarks : [image] You’ll then be able to read, and even edit, the adaptative original document from within that new dummy/replicant document. [image] [image] I deleted from the bookmark’s mirror file (on the right - bottom section) : [image] You can see there …

. . . . . . .

@tearaway

What is the best way for me to manage subdocuments (I am thinking of my understanding of them in Word, here) for reuse of them in multiple manuscripts?

Exact same answer as the previous.
. . . . . . . . .

@tearaway

Are there any warnings of mistakes to avoid before I go too far?

Scrivener can’t know what you intend to do. So, no ; not really. Unless it is an obvious misstep.
(I’m aware that’s probably not what you meant by the above question, so : )
My advice: first thing you need to do before you pour real time into real work is to make sure you’ve understood the backup system and you’ve got it set right.
Also – and not least –, go through the tutorial if you haven’t already. Your case is not so much of a “learn as you go” one. [Better: read the manual.] ← [I know, I know, … (either obvious or annoying), sorry.]

. . . . . . .
Hope this helps.