I think reflect site hierarchy to package hierarchy, is good idea because when the application is big, it is easy to find the panels. i always use like this.
Application > Module > view NM On Wed, Jun 17, 2009 at 2:07 PM, Frank Tegtmeyer <[email protected]> wrote: > Hi, > > is there one established way to generate a page hierarchy? > Or some best practices? > > I like to have a website (also a dynamic one) organized in a > hierarchical way like traditional static websites. This way > users can go to their desired functionality quickly and may > be able to even remember the associated URL. > > I assume I have to use bookmarkable pages somehow. > > Some questions remain for me: > > 1. Do I have to mount each single page or is there some > wildcard/regexp/inheritance mechanism like in Django? > 2. How do I organize my source files? Does it make sense to > reflect the site hierarchy in a package hierarchy? > 3. The site I develop has to use authorization. Is it > possible to get a user back to the bookmarked page that > he accessed after asking for authentication? > I think yes, but am not sure. > > Regards, Frank > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
