Greetings!
I’m writing on behalf of an in-house web team for a large educational institution serving over 30,000 students. We operate a diverse intranet site with over 20,000 pages, using a bizarre hodgepodge of Geeklog, Joomla!, OpenX, a defunct commercial CMS you probably haven’t heard of, and hundreds of static pages.
Maintaining what we have is extremely challenging for a two-person team, and we are desperate to consolidate into a single, unified system which automates the repetitive and gets out of the way when we need to do something out of the ordinary. After months of research and debate, we’ll be making a final decision next week, and nothing we’ve found is a silver bullet. We hope you can provide one.
We’ve narrowed down our list of options down to an ExpressionEngine-based site; a custom CMS based on either CodeIgniter, Kohana, or CakePHP; or perhaps most radically, abandoning the CMS altogether and returning to static web pages, which offer unlimited flexibility, easier backups, easier searching through a Google Appliance, and better security (you can’t hack a database that doesn’t exist).
Here are our major problems with ExpressionEngine. Hopefully, somebody will provide us with rebuttals that haven’t occurred to us.
1. Deep URLs - As I mentioned, our intranet is diverse. We simply have not found a way to fit everything into three URL segments, which seems to be ExpressionEngine’s limit without resorting to kludgy solutions like URL segment variables.
2. Multiple groups - We have a number of employees that need to post to multiple sections of our intranet. ExpressionEngine’s permissions are great if you can categorize employees into a single group, but that’s not possible for us. The only solution we’ve found is to create a new “group” with permissions for just one person.
3. Ease of use - I think EE is amazingly simple to use, and very flexible with its custom weblog model. (If we code it ourselves, we will probably base the administrative interface on a similar model.) However, our users still have trouble. Image handling is an example of a stumbling block - we have tried to explain the difference between the “Add URL” and “Add Link” buttons to our testers to no avail.
Keep in mind that while we are trying to unify our intranet, we are also advocating to an institution (I continue to use that word with the most optimistic of intentions) that is not convinced that the World Wide Web is more than a passing fad. Therefore, we need the usability and productivity gains from this transition to be immediately noticeable and easy for PHBs to grasp.
If our site was just a little bit more consistent or a little smaller, we would have purchased licenses already - we’re already sold on the fundamental concept of EE, just not the ability to scale it to hundreds of mini-sites with very little in common. Are we wrong?
Thank you so much for your help. We appreciate it more than you realize.