LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2014

CODE4LIB February 2014

Subject:

Re: Python CMSs

From:

Coral Sheldon-Hess <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 13 Feb 2014 16:58:48 -0900

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (95 lines)

Valid question, WordPress fans. :)

I've done a bunch of work with WordPress--that's what my personal site is
built in, as well as a couple of organizational sites I help manage, and we
have a multisite installation for our librarians to maintain their own
blogs/sites, here. I've even hacked on it, a little (not the WP core, just
my own installs). So I'm not considering it for this purpose in part
because I would like the opportunity to learn something else. I mean, I
*can* work in PHP, but it's not my favorite thing.

More importantly, though, I feel like some of the integration and API work
I want to do would be way harder in WordPress than it would be in MODx,
Drupal, Django, or any number of other tools. To be fair, I've never really
tried building database-driven pages in WordPress (except inasmuch as
WordPress *itself* is database-driven), but it just seems like it would be
... gross... I'm prepared to believe you that it might not be gross, but it
also wouldn't be any easier than doing the same stuff in my current CMS,
MODx. (MODx is way more flexible, actually.)

The goal, here, isn't "Stand up a CMS quickly," or obviously I'd pick
WordPress. It's "build something really flexible and extensible and,
hopefully, fairly pleasant to manage." And a sub-goal is that I'd like to
do all that in Python. :)

Does that make sense?

-- 
Coral Sheldon-Hess
http://sheldon-hess.org/coral
@web_kunoichi


On Thu, Feb 13, 2014 at 4:35 PM, Riley Childs <[log in to unmask]>wrote:

> Also you just described WordPress!
>
> Riley Childs
> 704 497-2086
> Sent from my superior my Windows Phone
> ________________________________
> From: Coral Sheldon-Hess<mailto:[log in to unmask]>
> Sent: 2/13/2014 7:15 PM
> To: [log in to unmask]<mailto:[log in to unmask]>
> Subject: [CODE4LIB] Python CMSs
>
> 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. :)
>
> 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 now.)
>  * 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 and big secret API-based
> plans, so easy JavaScript (preferably 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.
> * 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!
>
> Thank you!
>
> --
> Coral Sheldon-Hess
> http://sheldon-hess.org/coral
> @web_kunoichi
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager