Re: confused again: a "home page" can't be some special case
On 6/6/06, Mike <[EMAIL PROTECTED]> wrote: > Rudolph and James Bennett, did you create your own custom templatetags? > If so, how did you go about doing it? I've been working on building and > adding menus to django templates that are populated with other content > as well, and I'd be interested in learning about your approach. I'll be writing something about it on my blog the next day or two. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: confused again: a "home page" can't be some special case
Douglas, James, Wilson, Rudolph: Thanks - that clears things up. It's quite encouraging to see that we were pretty much headed in a viable direction. Dave --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: confused again: a "home page" can't be some special case
Just like James Bennett, I would use templatetags for suchs "blocks" with little bits of information. I even generate a menu by using a templatetag. Rudolph --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: confused again: a "home page" can't be some special case
Another option is to create it as a flat page with the url "/" and pull in all your content using template tags. On 6/6/06, James Bennett <[EMAIL PROTECTED]> wrote: > > On 6/6/06, Douglas Campos <[EMAIL PROTECTED]> wrote: > > 1) create a homepage app to aggregate it all (don't be worried, it can > > live without any models) > > 2) use whatever app you have, and throw a index() merging it together > > 3) Have it "belong" to one particular app/model, and use templatetags > to pull out other content. > > I do this on my personal site; the home page is the "archive_index" > generic view, wired up to my blog entries, then I have the rest of the > dynamic content pulled out by templatetags. > > -- > "May the forces of evil become confused on the way to your house." > -- George Carlin > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
