Develop own CMS or use existing CMS?
My question is, should I redevelop the site from the ground up, using all the tools I've learned since the first version was developed, or just go with something that's already out there. I understand that theres hundreds of CMS systems out there, but I'm concerned with the time it will take to use them properly.
For instance, is it worth the time to learn to develop for the CakePHP CMS (just to name one), or should I just develop my own from the ground up? If I'm going to spend hours and hours learning to write a module for CakePHP, why not just develop for my own back-end that I know in-and-out?
Anyone else been in this dilemma? Anyone have any suggestions?
6 Replies
@Smark:
I've decided I'm going to actually make the site into something.
Unless that "something" is a new CMS engine or framework there's nothing like squandering vast amounts of time reinventing the wheel to insure you never accomplish your real goal.
@Icoo:
Wait isn't CakePHP a PHP web framework (like Django for Python)…u can basically write any web application with that…maybe you meant one of the many CMSes developed with CakePHP?
I thought there was one that the CakePHP team had made and they called it CakeCMS. Either way, I mean a CMS like Joomla, PowerPortal (if thats still around), DragonflyCMS, etc.
@vonskippy:
Unless that "something" is a new CMS engine or framework there's nothing like squandering vast amounts of time reinventing the wheel to insure you never accomplish your real goal.
Well I understand that there are tools out here to do what I want, but is it worth learning to spend all this time programming modules for Joomla (as an example), when I could just go out and make my own CMS from the ground up? I'm all for cutting work down, just as long as its secure and I can customize it to do whatever I want (without having to rewrite much/any of the developer's code).
vonskippy, do you have any suggestions for a CMS that might meet my requirements?
Drupal and Joomla seem to be the two biggest names in the PHP CMS space. Which is best is a subject of heated debates but the general consensus that I tend to agree with is that if you're a programmer then you'll prefer Drupal.
Joomla might be easier to get started with and might do more by default "out of the box" but Drupal is a very flexible platform that will take you a lot further if you're doing anything out of the ordinary.
It seldom makes sense to build your own framework.
@tetranz:
Have you looked at Drupal?
Drupal and Joomla seem to be the two biggest names in the PHP CMS space. Which is best is a subject of heated debates but the general consensus that I tend to agree with is that if you're a programmer then you'll prefer Drupal.
Joomla might be easier to get started with and might do more by default "out of the box" but Drupal is a very flexible platform that will take you a lot further if you're doing anything out of the ordinary.
It seldom makes sense to build your own framework.
Definitely consider Open Source. I would addto the above. WordPress
@Smark:
vonskippy, do you have any suggestions for a CMS that might meet my requirements?
No, and any advice you get would be pretty shallow. No one knows better what you need (or are looking for) then you.
Your best bet is to spin up a local VM, load your top 5 candidates, and give all 5 a decent test drive. Pick the top 1 or 2 based on features (i.e. the two that closest match your wish list), and then examine the nuts and bolts of how they're built to pick the one which is easiest for you to understand (and therefore modify).
But remember - unless designing and maintaining a CMS is your final goal - don't get bogged down on the minutia. It's a web site - it doesn't have to be perfect (e.g. content is king).