views:

312

answers:

4

I have a php site setup with multiple controllers for the different sections of the site.
e.g index.php, gallery.php, faq.php etc.
Currently I have a base template which I call from each controller, which in turn includes the relevant content for the page. I also use tinymce to edit this content file. So it's really a very simple cms.

Edit: To clarify, I have several new features I would like for my cms. e.g Specific section editing, menu editing and a few others.
But I thought instead of continuing development on this and reinventing the wheel, I'd try to find a cms which can plug in to my multi-controller system, instead of forcing me to develop my app in it's framework. I guess I want it to manage just the content, not any other backend stuff of my site.

Hope this is understandable.

A: 

I'm not sure if I'm understanding your question correctly. You have a site with a basic CMS using a template system and multiple controllers. You don't want a framework to port your site to, but you instead want a CMS that will "plug in" to your current site? What exactly do you want plugged in to your site? (i.e. What features/functionality are you looking for?)

Edit: I still think you should consider an MVC framework like CakePHP if your goal is to build a more robust CMS without re-inventing the wheel. Building on a well-designed framework would also make extending your site's functionality in the future much easier (as well as make it easier to maintain a complex web application).

The only other option I can think of is to simply replace your existing CMS with a more robust one, like Drupal/Joomla/Wordpress, which you could then extend with modules. But that would probably give you less flexibility, not more.

Calvin
The only functionality my cms has is to edit the body content of certain pages. I would like additional functionality such as being able to plug in gui manageable menus,edit specific sections and other things that aren't coming to mind right now.
menko
A: 

Le me see if I have this right. You want a CMS. But it has to be one that will conform to your arbitrary way of doing things that you can drop in and have work. You want a CMS that isn't frameworkish at all. A CMS that will only do the frontend, and not the backend.

You don't want a CMS at all. A CMS, by its very nature, does backend work. That's the point of a CMS. What you want is Dreamweaver-esque magic template handling.

Or maybe you should adopt a real CMS or framework, and work from there. It's not really reasonable to expect this sort of magic psychic power from a CMS.

Kalium
I don't expect to get one to just drop in and work, but rather to be non intrusive.I guess I misunderstood what content management is supposed to mean, most cms seem more like website managers. Or perhaps I don't understand the intrusiveness required to manage content.
menko
On the vast majority of websites, with the exception of certain online services (online banking, search engines, webmail providers, etc.), the CMS basically is a "website manager" since the website's primary purpose is to serve up content. Which is why I'm confused what else is left for your back-end to do if not to manage content.
Calvin
Yes I suppose if you look at it that way, most of my codebase is a very specific cms, and I just feel bad writing the parts that are found in most other cmses.
menko
A: 

i also recommend Drupal. its very well organized and is easily adjusted to almost any style of website. you can use it as a pure cms or add plugins w additional features as needed .. the core package is fairly small, very easy to set up and play with, and very well supported .. worth looking at

Scott Evernden
Documentation should definitely be a major consideration when choosing a framework or an extensible CMS. That is the one area where I feel CakePHP is somewhat lacking.
Calvin
A: 

If you wrote a very basic CMS for your own use it seems to me that you should have no problem adopting an existing out of the box solution like Drupal, Joomla, etc. These are full featured CMSs that are ready to go and with some graphics work and a little hacking on your end can look like anything you want.

Your other option is using an existing framework like others have suggested such as CakePHP, CodeIgniter, etc. These are all frameworks which basically give you all the tools you need in order to build a more robust custom CMS than what you have now.

It seems to me that you know at least a little bit about what you're doing. I would suggest you check out the different frameworks that are available and run with that.

CodeIgniter

CakePHP

Pete
I have web sites running drupal and textpattern already, I just have wishful thinking of some kind of modular 'cms' with text editing,navigation and other components wish I can use with established codebases. :P
menko