> I'm not sure what you're looking for here. Designing a home page is not a django topic. Using django to deliver a homepage is the same as delivering any other page
Please don't take offense, Bob, I appreciate you taking the time to respond. I could not disagree with you more. Every web site has a home page. And by definition, a home page is DIFFERENT from all other pages. But the docs say nothing about any of that. Search them for 'home page' and see what you get. Django sets you up with a series of apps which, taken together, form your project. But in which of these apps does the home page go? Does it matter? Why or why not? Should you make a separate app for the home page? If so, why don't they tell us to put it in the app that is created with startproject? >> where to put the url >I don't understand what you mean by that. please explain I know that the url is r'^$. But if I knew what app to put it in, then I would know where to put this home page url. But what if the views and templates related to your home and other static pages (like About Us) have nothing to do with the views and templates of the rest of you project - aside, maybe, from the very basic common html? This is why people like jorrit787 and I struggle with the home page in Django, and why we would like a little guidance and some wisdom about best practices. >>And how to handle a complex home page with a lot of changing content - like on a newspaper, where Django was created? >Seems to me that's not a django issue. Again, with all due respect, I disagree. Why do we have filters like truncate? Isn't that so you can put a teaser on the home page and then link it to somewhere deeper in your site? Don't a lot of non-blog sites also have rapidly changing content? Member sites, fan sites, etc? Of course we can put an article on the home page, and the next day swap it out for a new one, but that's the most obvious way to do it. Is there a better way? What is the technology, coding, views, template set up and admin that best accommodate that kind of site? But we get no guidance on these things. And even if you think this is for designers and not developers, you have to remember that a lot of us are doing both, and even if we aren't, the designers and owners are going to ask us to put this together for them, aren't they? To the uninitiated, these are not small questions. And when you then try to configure your urls, it becomes an even bigger problem. And I think that the fact that you and other more experienced Django users don't see this as a problem is itself a problem. > And second, where (other than trial and error) do I find that kind of documentation / support? Trust me, I've googled this plenty, and the pickings are slim. On Tue, Feb 23, 2016 at 9:39 AM, Bob Gailer <bgai...@gmail.com> wrote: > > On Feb 23, 2016 7:59 AM, "Malik Rumi" <malik.a.r...@gmail.com> wrote: > > > > Why is there so little information in the docs > > Documentation evolves. User input helps that process. Perhaps you can make > a contribution as you learn. > > about how to build a home page > > I'm not sure what you're looking for here. Designing a home page is not a > django topic. Using django to deliver a homepage is the same as delivering > any other page > > where to put the url > > I don't understand what you mean by that. please explain > > whether or not to build a separate app around it, or why not to put it in > the folder with settings in it, > > If your home page is a portal to several apps then it seems to me you > would have an app for the home page > > And how to handle a complex home page with a lot of changing content - > like on a newspaper, where Django was created? > > Seems to me that's not a django issue. > > > > And second, where (other than trial and error) do I find that kind of > documentation / support? > > Google CMS? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/EMtRahO3EYI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CAP1rxO4_xrKa%2BtdZ4VoHVbwxuvj628D%3DgURg%3DqFP-8R8c9umTQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CAP1rxO4_xrKa%2BtdZ4VoHVbwxuvj628D%3DgURg%3DqFP-8R8c9umTQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAKd6oBz0j88G8JZGLRSbEQz5KnsiT084iE0sTKQ_bnjQHqfRDQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
