I'm relatively new to the features module and I've read contradictory recommendations online regarding whether it's easiest to maintain A) one big feature or B) several smaller features and then a "feature-controller" type module that lists all the smaller features as dependencies.
A bit about my specific situation: I'm using a
local development -> dev server -> staging server -> live server workflow. This particular site will almost certainly be the only one of its kind that I ever develop; I do not intend to use the
features I create for this site on any other sites.
This makes me lean toward doing everything in one big feature because I've had problems in the past where I accidentally defined the same rules in multiple features and gotten into trouble. However, in terms of structure this seems wrong to me-- there are different features/functions so they ought to be divided into separate features. On the other hand, I feel like by doing this I may just create additional work and overhead for myself that won't benefit anyone.
Which approach is easier to maintain in actual practice-- one big feature or many smaller ones?