I'm jumping into Django right now, converting from Zope, and wonder if anyone has any helpful thoughts or even hints about exactly what direction to take, given our situation. And perhaps this thread might be useful to someone else, since it's a fairly common scenario.
I'm building a typical software developer's site, with a handful of key products, each with its own overview page, documentation, FAQs, application notes/tips, walk-throughs, support, download files (release and beta), etc. Along with that will be a site-wide blog for news, releases, etc. I'd also like to have site-wide "cross-section" views of all downloads, all documents, etc. (easy with a database). And, of course, someday soon I'd like to have user fora (OK, forums ;-), an online store, user-accessible information about product serials they've bought, etc. Django seems like the best approach to make all of this practical and fun. But to avoid the typical "brochure ware site" problem with stale content due to (incredibly low, admittedly ;-) laziness/expertise barriers like through-the-web editing, I thought I'd make the site as easy as possible for anyone at our company to update, and make the interactions we have with the site be blog-like in as many places as possible. We'd use desktop blog clients like Ecto or MarsEdit for adding new information to the site in a wysiwyg fashion (including easy additions of FAQ entries, walk-throughs, beta & official release notes, etc.), especially for entries with embedded graphics (screenshots, movies). So perhaps the best structure would be something static using direct_to_template generic views for the basic (static) product/company info pages (using template inheritance for overall look'n'feel), but then using blog-like entries for all the dynamic stuff like FAQs, news, beta/normal releases, etc. But what about things that are more structured like walkthroughs (multiple such elements per product, multiple pages per walkthrough) or white papers, or, mostly importantly, online documentation? I'd like to make updating the documentation as easy as updating a web log entry, ideally. Should I define Models for documentation elements like Chapters, Sections, Subsection, etc., and relate them all logically in some kind of tree structure? How would one get a blog-llike view on those elements? And how would one piece them together logically without a lot of admin screen editing? Any advice/thoughts/laughs/hints greatly appreciated. I can elaborate if necessary, but my thinking is still a bit fuzzy as I'm trying to deal with several issues at once, and I'm still learning Django. Cheers! --Chris Ryland / Em Software, Inc. / emsoftware.com --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
