It really depends on what you're doing and the scope of your application. If it's just a fairly small app and it's never going to grow beyond this, then your current approach may well be fine. There is no universal "best" practice for these things.
While I wouldn't recommend using singletons for anything other than stateless leaf methods and/or one-way calls (e.g. Logging), dismissing it out of hand 'just because' it's a singleton isn't necessarily the right thing to do.
Having a few singletons is pretty typical and not usually problematic--a lot of singletons leads to some irritating code.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.