Re: Another Django CMS customization question
Hey Josh, I have written an CMS in django, and so have others. One of your major problems seems to be in the argument against using another template language for page rendering. Most people I have spoken to chose a lightweight markup language (markdown, ReST, WikiText,...) to do the actual page editing, since this removes the need to write arbitrary HTML. The thing is, Django's templating language doesn't write HTML for you (neither does RoR's?). It simply allows you to render a context in a very powerful way. If you feel as though this is what you want, you can easily use the Django templating rendering engine in your own view (a la http://www.djangoproject.com/documentation/templates_python/). Just to note, I wrote a pretty cool CMS-like application that does cool backend context generation in a couple days. (Granted I know django fairly well.) That being said, if it's just a CMS you want, why don't you like something already created? Cheers, Mike Axiak On Apr 4, 7:20 pm, "Joshua" <[EMAIL PROTECTED]> wrote: > Hello all, > > I am completely new to the Django project and have some initial > questions that I hope someone can answer for me. > > I have searched this group and the internet looking for this > information, however, I seem unable to find answers. > > First, a little background info. After giving rails a shot, I had some > difficultly getting started and came across Django - which, after > installing and playing around with a bit, feels much more comfortable > (I have a very small bit of experience with Python), easier to use, > and more extendable. It also seems to give you more functionality > right off the bat (admin, rss), which makes it faster to utilize for > real tasks like building a data driven site. > > While I was able to get a admin interface up and running in a few > hours, and believe I basically understand how the apps work in > relation to a project - I am starting to question whether it would be > better to build an CMS with another toolset/language or build on top > of Django. > > The specific task I have in front of me is to build a CMS that can be > customized for different sites and different "views" (templates) while > allowing a CMS admin user to add pages to a site - much like the > radiantCMS built with Rails (http://radiantcms.org/). However, unlike > radiant, I don't want to have to use ANOTHER template language (other > than the one provided with Django) to build my views. > > I have looked around for a project or code that implements this > feature using Django and haven't seen anything - is there something > I'm missing, or would this be extremely difficult to create? I would > be happy to contribute to a project or give this away upon completion > - I'm just wondering if Django is the right tool for the job ahead. > Honestly, the auto admin, and Django in general have me geeked - I > really want to focus on using it along with MooTools. > > Thanks in advance for your help, > > Josh --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Another Django CMS customization question
On 4/4/07, Joshua <[EMAIL PROTECTED]> wrote: > The specific task I have in front of me is to build a CMS that can be > customized for different sites and different "views" (templates) while > allowing a CMS admin user to add pages to a site - much like the > radiantCMS built with Rails (http://radiantcms.org/). However, unlike > radiant, I don't want to have to use ANOTHER template language (other > than the one provided with Django) to build my views. The important thing to remember here is the concept of a "project" in Django; each project, even if all of them share a single database, has its own settings file, and this is the key. In each settings file you can specify the TEMPLATE_DIRS setting, which tells Django where to look for templates; this means that, for example, you can have several sites which each have the same INSTALLED_APPS setting and the same URL configuration, but use completely different sets of templates to render their output. In fact, this is largely what we do at World Online: our sites share a database and use the same sets of applications, but each uses its own template set and so has its own distinct look and feel. For example: http://www.lawrence.com/news/2007/apr/02/serving_silence/ http://www2.ljworld.com/news/2007/apr/04/man_rescued_plymouth_church_spire/ Note the similarity in the URLs -- both follow the same pattern of "/news/", and both end up at the same view function in the same application, but the different TEMPLATE_DIRS settings for the two sites mean that the output can look drastically different. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Another Django CMS customization question
Josh, My first question would be if you've checked into flatpages yet. If I'm reading what you're asking, it solves the problem almost entirely. And, it's quite simple and you can use it to build more structure on if you need more features than it offers. http://www.djangoproject.com/documentation/flatpages/ On 4/4/07, Joshua <[EMAIL PROTECTED]> wrote: > > Hello all, > > I am completely new to the Django project and have some initial > questions that I hope someone can answer for me. > > I have searched this group and the internet looking for this > information, however, I seem unable to find answers. > > First, a little background info. After giving rails a shot, I had some > difficultly getting started and came across Django - which, after > installing and playing around with a bit, feels much more comfortable > (I have a very small bit of experience with Python), easier to use, > and more extendable. It also seems to give you more functionality > right off the bat (admin, rss), which makes it faster to utilize for > real tasks like building a data driven site. > > While I was able to get a admin interface up and running in a few > hours, and believe I basically understand how the apps work in > relation to a project - I am starting to question whether it would be > better to build an CMS with another toolset/language or build on top > of Django. > > The specific task I have in front of me is to build a CMS that can be > customized for different sites and different "views" (templates) while > allowing a CMS admin user to add pages to a site - much like the > radiantCMS built with Rails (http://radiantcms.org/). However, unlike > radiant, I don't want to have to use ANOTHER template language (other > than the one provided with Django) to build my views. > > I have looked around for a project or code that implements this > feature using Django and haven't seen anything - is there something > I'm missing, or would this be extremely difficult to create? I would > be happy to contribute to a project or give this away upon completion > - I'm just wondering if Django is the right tool for the job ahead. > Honestly, the auto admin, and Django in general have me geeked - I > really want to focus on using it along with MooTools. > > Thanks in advance for your help, > > Josh > > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
