How to organize views?

[eluser]Mr. Pickle[/eluser]
Situation
I find myself struggling with the organistation of views and controllers. I have read the main documentation about views but this is not actually diving into my problem, uhhhh challenge My website exists of a few main templates. Within these templates I have several views ('content blocks' as I call it myself) Some parts are the same for every controller but others may differ.

View management
What is the best practise for view management? I can think of the following possibilities, but I'm not confident enough they actually make life easier:
(1) Main template which checks for the passed views and shows only those filled.
Check within view what page is loaded so what content to view.
Downside: lots of coding within views.
(2) Several templates, having some views shared, for the rest the same as (1)
Downside: lots of if and elses
(3) Calling the views seperately from within the controller (so no template) and use shared views in which I check what page is loaded to determine the content to view
(4) Calling views seperately and have them unique for each controller (lots of duplicate coding, but again, some (small!) parts may differ throughout controllers)

Controller specific styles/scripts
Also I thought of setting a config array within my passed data array, summing up the styles and scripts I'd like to loop in the header file. Is this an 'accepted' way of using CI?

Help!
Hope someone can give me some good advice to start with or some good resource to find more info because I didn't manage to find them yet.