[Web4lib] CMS + homegrown code (making the transition)

[Chester D. Mealer]

This is why I recommend MODx. Of all of the different sytems I have looked at, it is the easiest to import homegrown code into. We have several forms all of which use a library card number for authentication (based off of Innovative's PATRONAPI). With the exception of 1 or 2 lines of code, I pretty much pasted my existing handlers and forms into the cms and went on with my life. The same with our code to pull the New York Times Bestseller list.

MODx does have a database API that can work with your existing databases and in some cases makes future coding even easier.

The only down side I've found with MODx is that if you want to use an external source to authenticate your users for content management (i.e. the ability to edit articles) it is slightly more difficult than some other systems however, the ability to cut and paste homegrown code outweighs that in my mind.


Chester Mealer
Webmaster
Rapides Parish Library
chester at rpl.org


-----Original Message-----
From: web4lib-bounces at webjunction.org [mailto:web4lib-bounces at webjunction.org] On Behalf Of Francis Kayiwa
Sent: Monday, October 19, 2009 11:10 AM
To: web4lib at webjunction.org
Subject: Re: [Web4lib] CMS + homegrown code (making the transition)


On Oct 19, 2009, at 10:35 AM, Ken Irwin wrote:

> Hi all,
>
> Taking the CMS question in a slightly different direction: I
> currently have a library website that's all done in hand-coded html
> + php. I'm interested in moving toward a CMS, but I'm afraid of
> "losing control". So much of our current site is custom-built stuff
> with a lot of PHP running in the background (everything from
> database-driven dynamic content for things like our list of
> databases to a homegrown equivalent of the Serials Solutions A-Z
> search).
>
> Can I have both?

Sure. It actually becomes an opportunity to improve the CMS.

>  Do any or all of the CMS products allow for plenty of custom
> content too?

If it doesn't you probably won't be choosing it. ;-)

> If I move to a CMS, what happens to my database-of-databases? My
> myriad homemade tools? Can I still leverage the power of that
> system, or replicate it in an easier-to-use form? I want to join you
> all in the 21st century where I don't have to do everything with a
> hand-crank, but I'm afraid of being boxed in by the limitations of
> "what someone else wants me to have".
>
> Any advice, wisdom, guidance, or horror-stories?

At the end of the day your question amounts to the need to master
whatever CMS you choose. You have listed above that your site has
custom PHP so I will assume you are comfortable in that. I would
expect most of the big PHP CMS' will be able to do what you need with
your plugging the holes by incorporating your hacks. You will just
have to learn "the <insert CMS here> way" of solving whatever problem
you are trying to solve. Ideally you will release your source and
others with the same problem will be glad for it and the CMS improves
as a result. As more people look at your code you end up finding it
improved by more eyeballs looking at it (scary at first admittedly)...
Everyone wins.

Go for it and good luck

./fxk



_______________________________________________
Web4lib mailing list
Web4lib at webjunction.org
http://lists.webjunction.org/web4lib/