I would definitely implement localization and stick to 1 code base as much as possible You can deploy the same project to different servers and set a fixed culturecode if you have to or let it depend on the user's browser Just splitting your code because you want different languages without a localization mechanism is a bad idea. It will be horrible to maintain I have 1 project running for different clients on different domains with slightly different functionality and different languages and I am still sticking to 1 code base for all of them.
I would definitely implement localization and stick to 1 code base as much as possible. You can deploy the same project to different servers and set a fixed culturecode if you have to or let it depend on the user's browser. Just splitting your code because you want different languages without a localization mechanism is a bad idea.It will be horrible to maintain.
I have 1 project running for different clients on different domains with slightly different functionality and different languages and I am still sticking to 1 code base for all of them.
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.