Earlier quoted context omitted.
I don't want to be defending the OP's position, but. . . settings.py is a mess. Even Simon's written a post bashing it ( http://simonwillison.net/2009/may/19/djng/ ). I cringe a little starting up a project and having to dive into the settings.py file. In some ways, Django tries to be flexible, but it's clumsy. For example, you can have your templates in your app directories. So, you have /path/to/project/posts/templ…
RE: "I often have to manage images/css/js manually, figure out where to put them, etc" This has (yay!) been solved in 1.3 with the inclusion of the staticfiles app. I now just put my app-specific static stuff in static/ and then run manage.py collectstatic and all is well in the world :)
I'd completely missed it. Thanks!