Does any CMS fit my needs? Using multiple CMS' for one site?

hello!

I have an established website with around 1000 static html pages I manage manually (not as bad as it sounds…maintainable, but leaves little time for developing new features). I’m purely a front-end designer, though I’ve been through a lot of PHP tutorials and understand the syntax well enough to modify pre-written scripts for my needs when necessary and fudge my way through phpMyAdmin for MySQL stuff. Creating my own CMS is not a possibility at this point.

Updating my site is a full time job, so stopping to port the entire thing to a CMS is not an option. What I’d like to do is start with converting my “site.com/NEWS” directory to a CMS so I can allow users to post company news stories with a GUI backend. Wordpress seems like the obvious choice here.

However, I’d eventually like to convert other directories such as customer support/faq to a CMS so our support staff can edit the content. Wordpress seems like a bad option here.

ExpressionEngine seems like a good choice, but the URL’s are not ideal, and from what I’ve read, installing it in multiple subdirectories requires multiple licenses.

What’s out there that will work for me? I know little about Drupal. Joomla is not an option (messed around with it, found it a little hokey). Any help/comments are appreciated!

Wordpress can be good for anything since it has billions of plugins.
Drupal is a constructor, you’ll have a hard time with it.

can you define “constructor”?

Worpress is “turnkey”, “ready-to-go” even without plugins.
With Drupal, you will have to plan first. Define taxonomy, node types, install plugins (handlers) for proper content types, and then you will maybe be able to add the content.
But don’t rely on my opinion, I’m not a Drupal guru :slight_smile:

I can’t tell whether that’s a really horrible review of Drupal or a lack of confidence in my abilities :lol:

OK let’s just bump this thread until some guru stumbles upon it :slight_smile:

EE sounds like a good fit here and would allow you to manage all your content from the oneCMS.

  • URL’s aren’t a problem, you can have site.com/news , site.com/support , site.com/about and so on
  • you can also restrict your admin users to only be able to manage the bit’s they need to, ie support staff can only edit support content
  • You only need one licence if you want to use a “subdirectories” URL structure, if you want to run multiple site, ie sitea.com siteb.com sitec.com then you’d use the Multi Site Manager addon but I don’t think you need this

so EE would allow me to install EE in the root, leave everything untouched except for site.com/news (to start), and then bring the other directories into EE as I desired?

And as far as pretty URL’s go, is what you say now true in EE 2.0? I don’t think that was the case in EE last time I checked.

Yes that’s pretty much is, one install in the root , then EE will control everything else however you want it to, ie different sections of the site, news, support etc, all of which you can just introduce as and when you want.

In EE, “pretty url’s” are started using .htaccess (where supported) by removing index.php - there’s an addon for EE1.6.x that automates this but it hasn’t been ported to 2.0 yet. However there’s nothing stopping you writing your own .htaccess. The rest of the URL you can define yourself using a mixture template group names, template names, content titles, or even your own custom combos. Building URL’s is exactly the same in 2.0 as it is in 1.6.x.

Don’t forget that 2.0 is still in beta so for a mission critical project I’d suggest sticking with 1.6 until the first stable version 2.1 comes out, then you can upgrade at your leisure.

cool…maybe i’ll look into EE further

you can have site.com/news if you want? i thought you had to do something like site.com/templategroup/news

Movable Type might be able to help you here.

Though I am not experienced with it, Expression Engine sounds like a good choice. You can definitely have the sort of URLs you are after, and manage only certain directories if you want to. If you need help setting up this sort of thing, the EE community would likely be very helpful.

Just name your template group “news”, that would give you site.com/news, then an article page might be site.com/news/my-article-name or if you have a comments facility in use something like site.com/news/comment/my-article-name (where “comment” is the template name).

One thing I’ve found with EE is that, if you are using a .htaccess script to remove the index.php in urls, you have to explicitly make exceptions for files outside the CMS. Easily done, though.

There are lots of other CMSs out there, of course. At the moment I’m playing with Silverstripe, which is very impressive (and free!).

What do you mean Joomla is “hokey”. If you don’t like Joomla, then I think you will like Drupal even less so. Because Drupal has a really steep (and I mean steep) learning curve. Has nothing to do with your abilities. It just takes a lot of time to learn.

That is why my first impression for your site would be Joomla. Joomla since you got so many static (non-blog) pages – did you say 1000?

But if you don’t like Joomla, then go with Wordpress. It is the easiest of the three to use and good for blogging. You can use it to create static (non-blog) pages as well.

See comparison of Wordpress, Joomla, and Drupal here.

As someone stated before, Expression Engine is the way to go.

Its very scaleable as it comes with a ton of features right out of the box.

You can have clean URLs even in the current version. I think thats more of a server side setting anyway. There are a couple of ways to achieve the clean url look but the easiest is with .htaccess if you are running Apache.

If you are running IIS, then I think the new Windows Server 2008 will allow for URL_REWRITE, which will allow you to remove the index.php from the URLs.

I’ve used Wordpress, Drupal, Joomla. I find Wordpress to be excellent for BLOGS. It’s almost a standard for Blogging. However, EE has blogging capabilities too. There is a free version of EE, but its pretty much stripped down. You are better off getting the personal license or commercial license.

Wordpress is also somewhat difficult to modify. EE is not hard to modify at all. Its accepts standard HTML / CSS and EE has its own set of tags that make it pretty easy to use. There is a bit of a learning curve but once you get the thinking down, you’ll be like “oh, thats very easy!”

Say, your news section is going to look completely different from the rest of your site. Its very easy to create a new template group and create a new template, add some EE codes, and publish that page.


does your homepage of your currently existing site use index.php? or are you on index.html? do you have an images/ folder?


You might consider download EE CORE. Its free and will let you test out EE and learn EE template system. Its very fun to use. EE is the best CMS I’ve used and its price point can fit anyone’s budget.

oh also, setup a development area, i wouldnt upload EE to your LIVE site. In fact, you may want to upload your current site and then upload EE to the same place and see if you can install it. See if it can co-exist with your current site. You might overwrite or have files of the same name that EE uses.

Anyway, if you have any question you can PM me.

Hey Kevin Yank.

I don’t work for EE. I’m not affiliated with EE in anyway, except I’ve used it alot.

I’m interested, since you are a PHP Guru, if you would be interested in giving EE a trial run.

Its very extendable. You can set your Template to accept PHP code so you can pretty much can write anything you want in your templates, but most of the time you will find there is a EE Tag that will do what you want. It has its own language, which is very easy to understand and use.

Also remember, EE was made by the same company that makes Code Igniter, and thats a very solid framework.

EE is rather nice. I would have hitched my wagon to it when freelancing if the then-licensing situation wasn’t a little onerous.