watching the pycon and django talks now (and it looks super cool) ... but at least by what I see so far is that its trying to allow people to download and create an "even more batteries included" type of platform. I'm hoping to create a repository of templates and designs (more for learning and examples), not necessarily an integrated platform.
On Jan 2, 2:02 pm, Jim White <white.j...@gmail.com> wrote: > If you don't already know about Pinax perhaps you should look > athttp://pinaxproject.com/. They already provide some of this and (as a > Pinax user) it would be nice to see some template compatibility. > Unfortunately they are still sub 1.0 in their release but it looks > like they have settled down a bit in their base.html and css. > > On Jan 2, 10:16 am, Will Dampier <judow...@gmail.com> wrote: > > > oooo ... I do like the idea of having a handful of "standard django > > plugables" like django-registration, django-cms, django-profiles, and > > dozens of others ... the Django-Resources page would be a good place > > to start. > > > Then designers could upload either a full "website layout" against all > > of my, and the "plugable", views or simply a against a subset of the > > "plugable" applications. If I "standardize" the blocks that the > > designers are allowed to use, then for any missing templates I could > > just implement my default template. With some sort of trickery I > > could even allow people to create mash-ups combining different > > designs. > > > On Jan 2, 12:58 pm, Raja <rajas...@gmail.com> wrote: > > > > IMO, it would be useful if we get standard templates for django > > > libraries that are out there, like django-registration, django- > > > profiles etc. Since the library offers the models and views, it would > > > be helpful if the templates are also available. The developer could > > > then take it and modify it to adapt to their website. > > > > Also, frameworks like Blueprint CSS (http://www.blueprintcss.org) make > > > it much easier to start designing a layout by providing a pre-defined > > > template , so its not all that difficult now, but blueprint could be > > > one of the templates thats available in the original poster's library. > > > > -- Raja > > > > On Jan 2, 6:01 pm, Dougal Matthews <douga...@gmail.com> wrote: > > > > > How would you propose people edit and manage the templates? > > > > > Do you follow a wiki style where everybody can edit others? or follow a > > > > VCS > > > > and allow forking of templates? > > > > > I think it will be hard to find contributors since it will be hard to > > > > have a > > > > limited/standard template context that still remains a useful resource > > > > for > > > > all. > > > > > Have you any thoughts about example templates? Perhaps a good place to > > > > start > > > > would be by creating custom admin templates as that context is defined > > > > by > > > > django already (pretty much) and then it would be useful and usable by > > > > anybody in real projects rather than scenarios. > > > > > Dougal > > > > > --- > > > > Dougal Matthews - @d0ugalhttp://www.dougalmatthews.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-us...@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.
