I don't have any professional experience with Django-CMS, however I did dive into it and try out their demo site and even test out an installation myself on a server. My first impressions via the demo site they provided were very good, I enjoyed the feel of it and how easy it was to add content and build plugins. The installation onto a server is a different impression all together... Firstly they didn't provide the nice templates to start out with like they provide with the demo site, so figuring out how to build the template and set-up the JS/CSS was interesting. On top of that, following the installation guide was a failure, and couldn't get it to run properly. I ultimately used the quick start guide to get it up and running much more quickly.
In the end, the installation could be much more elegant, rather than having to jump through hops to make it work. Comparing this to the installation of Pinax, I really enjoyed how much effort that project put into making Pinax as easy as possible to get an environment up and running. In the end, I'm more of a developer who likes to build the project from scratch and add reusable apps as I see fit. This way I have full control over what apps are included in my project. I will recommend attempting to convert the backend of your companies current CMS to Django. If the frontend is not as meshed with the backend code, there should be little problems with interchanging the backend to a Django-based solution while keeping your awesome sounding frontend that's tried and true by your clients. I recently converted an old PHP site's backend, keeping all the same HTML/JS/CSS files almost the same with little modifications, only needing to change the path which AJAX connects to on the server. Mind you, in this project I didn't have any PHP code embedded into the HTML file, which shouldn't be done anyways. Backend and Frontend code should always remain separate, it makes the parts easier to interchange and port to newer backend platforms in the future. On Oct 6, 3:57 pm, colinta <coli...@gmail.com> wrote: > I would love to hear some professional opinions on how easy it is to > create, maintain and support a DjangoCMS-based website. The only > curve ball is that the client will need customizable forms. Otherwise > it's a pretty standard site. > > Very recently - last week - the company I work for announced that we > are switching from PHP, where we have built a robust lovely framework > (in PHP, though, so ug) and really whiz-bang-neat CMS (very drag-and- > droppy, clients love it). We've settled on Python+Django as our new > stack, where we will call upon the resources of the open-source > community so that we can focus on *building sites* rather than adding > features and bug fixing our internal framework. > > But the question remains open whether we should build this *next* > project using our tried-and-true framework & CMS, or whether we'll use > DjangoCMS for the first time. > > So whaddya say! Any thoughts? Strong opinions one way or the other? > I will really appreciate the insight. -- 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.
