On Oct 7, 2:22 am, Kevin <kveron...@gmail.com> wrote:
> 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.
I have a couple years of professional experience with django-cms. It
has been a while since I pulled the latest download from github and
did a fresh install, but my experience with installation in the past
is different from Kevin's experience. They provide an example/default
django-cms project you can use which includes templates, js, css, etc.
Granted it is pretty minimalistic, but it is there (or at least was
there when I last installed it).
> 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.
>
It would be helpful to know some details about Kevin's target
platform, what problems he experienced, etc. Installing django-cms is
certainly not a 'one-click' sort of endeavor; it's a far cry from
Wordpress's installation experience, for example. However in my
experience the installation guide is quite reliable. I typically
install on a debian or ubuntu server, and I suppose I do deviate from
the installation guide a bit because I use virtualenv. But django-cms
is one of the first things I installed in my quest to become
experienced with django, and I found it manageable.
The other thing you could look into for deployment is a configuration
management tool like chef or puppet. You may be especially interested
in this: http://help.opscode.com/kb/otherhelp/build-a-django-stack
Regarding the original post...
> On Oct 6, 3:57 pm, colinta <coli...@gmail.com> wrote:
>
> > 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.
I got the impression you were in the process of leaving behind your
tried-and-true PHP framework in favor of adopting a community-
maintained django-based CMS framework so that you can focus on
building sites rather than developing your own internal CMS. That
being the case, I don't understand what you are asking here. Are you
considering building your own CMS again, this time in django instead
of PHP? Wouldn't that put you back in the business of developing a CMS
framework instead of building sites?
At any rate, unless you have a compelling reason to do otherwise, I
would heartily recommend using and contributing to one of the existing
django-based CMSes out there. Django-cms would be a fine choice in my
opinion, but if you want to look at some other options you could
evaluate Pinax [1] (as Kevin mentioned), Feincms [2], Mezzanine [3],
and Mingus [4].
Hope that helps, and good luck!
1: http://pinaxproject.com/
2: https://github.com/matthiask/feincms
3: https://github.com/stephenmcd/mezzanine
4: https://github.com/montylounge/django-mingus
--Stuart
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment