I'm currently looking at some of the areas of Scrivener's interface that could be simplified. (Not dumbed-down, mind - I'm not interested in removing features, only in making existing features easier to access.) One of those areas is Compile. We tried to do this not long ago by introducing the "Summary" pane, which presents you with only the most commonly-used Compile features. However, I've had some ideas about how to make that pane even more useful.
The "All Options" pane is going to stay - it's important that users can take complete control over the Compile process, even though the options available are necessarily complex in order to allow for any project structure. However, I'm thinking of modifying the "Summary" pane to make it much more of a one-stop place for new users, so that users who are compiling using common project structures won't need to play around with the full power of Compile unless they really want to.
As part of this, Scrivener will need to ask the user for a hint as to the structure of the project. I'd therefore like to get some idea of the sorts of structures that people use in their Scrivener projects, and would thus be grateful if as many people as possible could take this poll or reply to this thread.
For book-length works, these are what I assume would be the most common structures:
Parts folders containing Chapter folders containing text documents acting as scenes/sub-sections:

Parts folders containing text documents that each serve as a whole chapter:

Chapter folders containing text documents acting as scenes/sub-sections:

A bunch of text documents that each serve as a whole chapter:

I'd love to get a better idea of the sorts of structures that people are using, though.
Thanks for taking part!
All the best,
Keith