-----BEGIN PGP SIGNED MESSAGE-----
On 02/13/2014 07:13 PM, Coral Sheldon-Hess wrote:
> Hi, everyone!
> I've gotten clearance to totally rewrite my library's website in
> the framework/CMS of my choice (pretty much :)). As I have said on
> numerous occasions, "If I can get paid to write Python, I want to
> do that!" So, after some discussion with my department
> head/sysadmin, we're leaning toward Django.
> Here's a broad question, re: Python and Django: If you've made the
> switch, what has your experience been? Has Django (or any other
> Python framework) given you something cool that was lacking in your
> previous language/framework/CMS? Has it helped you build something
> awesome? Have you found it enabling or limiting in any way? If you
> were going to sell people on (or against) using it, what would your
> arguments be? I'm a relative newbie to Python, and a total newbie
> to Django, so even if there was a tutorial you found useful, or
> some caveat you learned along the way, I'm interested. :)
After you play around with their really good tutorial from the Django
Project I recommend getting the 2 Scoops of Django book. You won't
regret that and any person you ever collaborate with will thank you.
At my last job we went back and forth between Web2Py and Django and by
the time I left Django "won" out. The big reason was just the number
of people using it. It made it easier to play "Google Bingo" when we
ran into problems. I personally pushed hard and lost out ;-) for
Web2Py and my biggest reason was Web2Py guaranteed backwards
compatibility which made maintenance *ahem* easier. (Like I said I
lost out. ;-))
> And then a more specific question: Given the following
> requirements, do you have a Django-based CMS you'd recommend? (Of
> course, I'll also do my own research, but I'd love to see what
> other libraries' experiences have been and what's popular, right
I took Mezannine for a walk with an eye towards moving to that if we
ever scuppered our Perl based CMS. It was turnkey and my foggy memory
> * There's a chance we'll want to offer other editors access to it,
> at some point, so it would be nice if I can provide a WYSIWYG
> interface, which I also am going to want the option to *turn off*,
> for my own sanity. * We're a Springshare-heavy library with Summon
> jQuery) integration is a must. * It should play nicely with MySQL.
> * Because I probably won't be here forever, it's of the utmost
> importance that whatever we end up with is easy to maintain.
It is well documented and supported.
> * I'm used to MODx's page-ID model, where I can move pages around,
> and as long as I don't delete/recreate a page (thereby changing its
> ID), I don't have to change any links anywhere else in the CMS. I'd
> really like something that will work equally well, since the odds
> that I'll nail the information architecture on the first try are
> probably slim. :) (Maybe this one should go without saying, since I
> know WordPress and many other CMSs do this, but if you have to err,
> err on the side of being explicit, right?) * A nice forms-builder
> plugin (module?) would be a great thing to have, as well. We use
> FormIt in MODx, and now I'm spoiled.
> And, I mean, if there's a CMS on top of another Python framework
> you think I should be considering, feel free to throw that out as a
> possibility, too!
Flask is lean and mean and stays out of the way but most of what I've
done with it is Mickey Mouse projects. Like I said Web2Py is also a
decent framework and worth taking for a spin.
> Thank you!
The fortune program is supported, in part, by user contributions and by
a major grant from the National Endowment for the Inanities
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----