Where does backend belong to in Zend Framework?

Definatly belongs in a new module then it is easy to create a separate layout in my opinion.

Definatly belongs in a new module then it is easy to create a separate layout in my opinion. In a recent project a colleague created a separate admin controller in each module with the layout defined in an admin module. This way he could drop in/remove modules from the project with the main admin module autodetecting which modules are installed and creating menus based on the admin controller found in each pluggable module.

I have explained that poorly, but it's a good system.

I would create a separate module. Otherwise you might run into context issues because the ArticleController in the frontend should have other/limited functionalities then the administrative ArticleController and you end up implementing mixed controller classes (bad idea! ) or prefix the administrative class.So having multiple modules makes it easier to separate different concerns.

(Plus it will make it easier for you to implement an ACL and handle the corresponding resource/role definitions. ).

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.