Heya, I personally used the second approach, where the difference is basically that the second application just enables some administration modules that are not available in the frontend version. I structured the frontend services so that they can be re-used by the ones dedicated to the backend anyway.
Marco Pivetta http://twitter.com/Ocramius http://marco-pivetta.com On 24 September 2012 12:44, Paladyn [via Zend Framework Community] < ml-node+s634137n4657089...@n4.nabble.com> wrote: > Hello! > > I`m writing new CMS in ZF 2. First approach to new version of this great > framework is a bit tough for me. Especially in plan of structure of > application. So my concern is about better approach to CMS structure. > > I wonder is it better to build one application based on two modules: > Application (front application for user) and CMS (admin application) > or > build two separate zend applications (redirected by htaccess) with modules > based on functionality (like configuration, news, gallery...). > > First approach seems to be harder to fit to different clients needs > (configuration of whole application in one module.config.php file, > disabling one functionality would need to recode few files). Still it`s a > bit easier to write with ZF 1 experience (it looks so at least). > > Second approach seems a bit weird (building two seperate application when > it`s actually one - CMS without front application is useless) but > application configuration seems to be much easier. Every functionality will > have own module, so it will be more mobile and easy to adopt to specific > client needs. Still I can`t used to think about application this way after > my ZF 1 Cms. > > I`ll be very grateful for every help to understand new framework better > and to build good new CMS on right structure. > > (sorry for my bad English, I would like to share more thoughts but my > English seems to me too limited). > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://zend-framework-community.634137.n4.nabble.com/CMS-application-in-Zend-Framework-2-tp4657089.html > To unsubscribe from Zend Framework Community, click > here<http://zend-framework-community.634137.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=634137&code=b2NyYW1pdXNAZ21haWwuY29tfDYzNDEzN3wxNzE0OTI1MTk4> > . > NAML<http://zend-framework-community.634137.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/CMS-application-in-Zend-Framework-2-tp4657089p4657090.html Sent from the Zend Framework mailing list archive at Nabble.com.
