On Tue, Jan 8, 2013 at 9:52 AM, chad petzoldt <cpetz...@gmail.com> wrote: > Right now my project only has 2 apps that use a database (*real* apps). The > rest of the website is composed of many custom views, scattered all over the > place. I am new to Django, and I havn't quite figured out how to structure > my project directory just yet.
Every project needs to be rewritten once! (or so they used to say) > I think what I should really be looking at is the beginnings of a Content > Management System. But at this point, I think that is too far over my > head.The other *issue* is related to my design/develop workflow. Working > completely through an internet browser just isnt possible for 80% of the > project cycle. We have many programs which want to work directly on the > filesystem (on an offline machine), mostly coming from the Adobe Creative > Suite. > > There are all kinds of media documents and markups forming "Articles". > These Articles are passed around as bundles during design, and then when > they get to me I have to tie them together very neatly and push them onto > the website. The one thing I do have control over is the Url layout, and the > navigation of these articles. You have actually just spelled it out for yourself. Make an app that looks after Articles. Each Article can have Many to Many/One links to files (the "bundle") as models.FileFields (django-docs-1.4-en/ref/models/fields.html#filefield ) NB: I've never used these and haven't read the docs thoroughly. The phrase tie them together neatly isn't expressive enough. What are you putting together? Are you taking InDesign files and creating css/html/js? Are they pdfs? > Should I be splitting each of these "articles" into their own apps (a > directory with little more than 'templates/' and 'static/'). This makes > synchronization easy with the server, there is no database interaction > required; the only task left after the sync is for me to update my > navigation widgets (which I currently just do by hand). I think that splitting each article into it's own app sounds like a disaster waiting to happen. A massive clusterfuck of disaster. The idea of apps is to abstract out any commonalities to make workflow and presentation more simple. It is possible, but you need to do the mental abstracting. Personally I use trial and error - implement obvious solution, make changes as more complexity is required. My sites are simple. For more complex apps, you might want to sit down with a text/UML editor and flesh it out first. Get other eyeballs on the abstraction too! Cheers L. > Am I going the right direction here? Is there some App that helps me > accomplish this task a little cleaner. I think what I really want, is an App > Application (hotplugging apps or something like that). > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/yJsqstRt2JIJ. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. -- ...we look at the present day through a rear-view mirror. This is something Marshall McLuhan said back in the Sixties, when the world was in the grip of authentic-seeming future narratives. He said, “We look at the present through a rear-view mirror. We march backwards into the future.” http://www.warrenellis.com/?p=14314 -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
