That's usually an OK way to start, as you can always move things into modules later. Gotta love the routing control :)
On Sep 24, 11:28 pm, julien <[EMAIL PROTECTED]> wrote: > Thank you both of you for your answer. > I did it the way Tom suggested as the frontend will stay quite simple. > > On Sep 24, 3:04 pm, Tom Haskins-Vaughan <[EMAIL PROTECTED]> > wrote: > > > For the backend, I'd definitely agree: one module per section. > > > For the frontend, in my opinion, it depends on the complexity of the > > section. If there's likely to be more than one page per section, use a > > separate module. But if each section is just one page, I'd be tempted to > > keep it simple and just use one module with a different action/template > > for each. > > > Hope that helps. > > > Tom > > > Bruno Reis wrote: > > > one module per section > > > > 2008/9/23 julien Bessiere <[EMAIL PROTECTED]>: > > >> Hi, > > >> I'm new to symfony and I wonder how I should structure the website I'm > > >> working on. > > >> I plan to have to apps: frontend and backend. > > >> But within this apps, should I create one module per section (i.e. home, > > >> publications, news, research, team) or create just one module and > > >> different > > >> templates for each? > > >> If I understood correctly, the structure of the backend is the same? > > > >> thanks > > > >> Julien > > > -- > > Tom Haskins-Vaughan > > Temple Street Media: Design and Development for the Web > > [EMAIL PROTECTED] |www.templestreetmedia.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
