SuperSatellite ||

Assuming my brain is still functioning on a level that facilitates higher math (e.g. addition), I have currently not been to bed in thirty-five hours (thirty-six by the time I finished this). So…take that in to account if this lacks any discernible level of c….co…coherency. I wish I could say that I was pretending there, and that I did know that word from the start. I did not. My brain is being fueled only by Coke and sushi at the moment.

Travel was long. Pretty self explanatory.

I did get all checked in to the hotel in time to make it to the pre-conference training sessions though. The first one dealt with handling the reporting mechanism in dotCMS. It’s a neat deal, as they have incorporated the Jasper Reports system as the driving force behind report output. What this allows you to do is download iReports and craft custom reports based on any data in the database that you want to. You can take it about as far as you are able to based on the permissions to the database you have. That might be duplicating Google Analytics like reports, user tracking metrics, or any combination thereof. The framework allows you to call and compile any data in the database you like, and input parameters such as dates or titles as control mechanisms. And we aren’t just talking reports like the top ten pages for a site. You could do the top ten pages visited by the top fifty most frequent users between January and July. Through their use of the Jasper framework, you aren’t limited by dotCMS’s code to get the information you want. I’d be lying if I said it all made sense. The concept is simple, but I could easily spend weeks learning the intricacies of iReport. They did say that the 1.6 release of dotCMS should come with a few basic reports installed, so you could use them to see how to structure more custom ones.

The second session dealt with the built in form handling. There is a document available which discusses most of the ins and outs of using it, and this was pretty well contained within the scope of that guide. Most CMS (Content Management System)’s come with some level of form handling these days. There’s some room for improvement here, such as the fact that the only access control resides at the portlet level. If someone is granted access to the web forms portlet, they can see results of any form that you have created. It’s nice since the form handler is built in and just works as a feature, but you must keep in mind it will still require you to write the code for the form, and set up any logical branching or such that needs to take place as it is filled out. And because of how the data is stored and extracted, I would be concerned about the ability to poison data entered into a form. I’m not saying it can happen, but just that I see a potential for it. Hopefully they’ll add on some kind of GUI front end that end users could use to build forms, that will be very helpful since at the moment you really need the forms to be made by someone familiar with how the handler works. But as far as I am concerned, forms will be a headache no matter how good your tools are. End users will always find a way to break or otherwise screw them up, heh.

I missed out on the end user training session and updating from SVN session due to having not mastered being in two places at once. I apologize. The guys have been really great though, and in just an afternoon I’ve gotten a ton of great info. The developers and programmers for dotCMS are all very great people to work with, and they have been happy to share ideas and insight into things, which is nice. When was the last time you met someone deeply involved with actually making Drupal or Wordpress? Here, the developers are both names and faces. The same folks responding on the mailing list and helping in JIRA are the ones going out to eat with you.

I’ll be back with more info as things continue, and after I get some much, much, much needed sleep.

I felt it was time to take a closer look at a content management system I am getting very involved with. One might say I’m drowning in it. I prefer to think of it as being choked by it, heh. Really, it’s a very interesting system, and a fantastic tool for the price (free!). I have worked with a number of CMS (Content Management System)’s over the years: Coranto, e107, Joomla, Mambo, Wordpress, Drupal, and a few others that I’m sure I’ve forgotten about. It’s easy to get locked into one or two for various purposes, which had been true with me for a long time. The problem is, my short list there is only good for small to mid range sites. Now I’m webmaster for a site of better than 10,000 pages and 70+ editors. Those open source solutions don’t easily or always comfortably scale up to those needs.

That’s where enterprise grade content management comes into play. Swinging big price tags, naturally. You start learning names like RedDot, OmniUpdate, Hannon Hill Cascade Server, Serena Collage (discontinued), and Ektron cms400.net. You also learn they don’t come cheap, some breaking the $80,000 mark. $15,000 in this group is cheap. In some cases, you don’t even have to host it. But the support, features, and scalability you get from this class of tools is in a different league. Wouldn’t it be nice if you could get the best of both worlds though? Something like a Typo3 or Zope/Plone system, but with enterprise grade support and a learning curve within reach of your users? A tool that was open source to boot? Generally there just isn’t demand for this sort of software, at least not enough to make a successful project, it’s enterprise grade and enterprise cost because it’s an enterprise market. However dotMarketing has stepped up to the plate. They have developed dotCMS to augment their design and consulting business, but released it free, charging only for support.

I need to be fair though. dotMarketing really stood on the shoulders of the work done at the Liferay Portal project, that’s where it started. Liferay is the underlying framework that drives dotCMS, written in Java, and running on top of Apache Tomcat. But they forked the project and went a long way towards customizing everything you see and interact with. It isn’t just a fancy admin theme dropped over someone else’s work. It is also tied together intimately with Apache Velocity, which is very slick for writing dynamic templates. Needless to say, this isn’t a simple one-off , self contained type of application. It’s build on several different technologies, all open source, to try and provide the best of each tool to the end user. When you download it, everything is packaged up that you need though, you don’t have to hunt anything down separately.

This does make it more complex than other open source CMS options. Systems like Wordpress or Drupal can be installed to any server that runs PHP and a flavor of database server. On the other hand, dotCMS requires you to have root access to the server to install things like the Apache Tomcat server. This requirement has hurt dotCMS’s market penetration, as many web site owners do not have that kind of server access, opting instead for cheaper hosting solutions. That is a shame, because dotCMS is easily one of the most powerful open source options available, with a much shallower learning curve than equally flexible solutions (I’m looking at you Typo3). It’s also pretty resource intensive, so you won’t be dropping this onto a lightweight web server you built five years ago on an old AMD K6-2 system you had lying around. Plan on needed a couple gigs of RAM and a modern processor to heft it. You can run it in a dev environment in a PC okay, but not with less than a gig of RAM (I know, I tried, I failed). It might be open source, but it is truly enterprise grade, and is built for an environment that reflects such.

Part of what makes dotCMS so good is the way they approach content. As an administrator, you can create structures. These structures result in a form-like input system, that allows you to pull out some or all data for a type (say, a news posting, or product review). Any structure can easily be attached to an RSS feed. Each structure is unique, but can be dynamically related to one or other other types of content in other structures. For instance, you have a structure for “blog posts” and one for “comments,” and the comments can be related to blog posts. But you could also relate certain comments to articles, or news postings as well. This is a basic CMS feature used in most systems, but with dotCMS you see exactly how it works, and can modify or expand it. Better yet, create your own. Players related to teams related to sports. The flexibility allows you to develop to your heart’s content. And you don’t have to be a programmer to do it. Admittedly, relationships aren’t super easy to understand out of the gates, but an example or two gets you going. They really got things right with regards to how content should be created and used, and did a good job taking the cork out of the bottle for the end user to go nuts with it.

Speaking of examples, they do have a complete demo site running that allows you to both test things, and also see how certain things are accomplished. This can be very useful if you want to duplicate some kind of functionality, but need an example. They also outline plenty of macros that allow you to easily accomplish common tasks, like creating slideshows, navigation, MP3 players, RSS feeds, and more. One thing their demo site doesn’t showcase is that it can even run multiple domains through one back end, so you could be running demo.site.com, and blogs.site.com, and www.site2.com all through that one instance of dotCMS.

If you would have asked me before, I probably would have said that Drupal or Typo3 had the best permissioning systems available in open source. That’s no longer even remotely true. dotCMS has a fantastic permissioning system that allows granular access to both content and admin areas. Groups are used to define what a user has access to at the back end, while roles determine what they can use, see, and access with respect to content. This combines with a workflow system that can be used to make sure content is properly reviewed and approved before it hits the page. It’s simple, and it works. Well. On the user side, you can easily tie into an LDAP or Active Directory environment, though it requires manual set up. Users can be tracked through the system to provide some basic analytical data, and attached to CRM functionality to label, organize, and communicate with them. This goes far beyond any other competitive product in open source.

Where it’s lacking: documentation. Right now, it’s pretty scattered and different documents can be out of sync with others. I understand this is changing, and that they are moving to a system a la Apache’s documentation method. It is definitely needed. Luckily, their mailing list is pretty active, and they tend to be responsive on bug reports. I think it would be nice to see a little more stuff built in by default. For instance, dotCMS can be a blog, or host them, but you have to build the structures and relationships yourself. Tools like that are common enough that it wouldn’t hurt to just have it already set up. There is also no file structure, in the normal web sense, so no FTP (File Transfer Protocol) type functionality, you have to upload through the system or via WebDav, if your server supports it.

I will be at the dotCMS Open Minds Conference next week in Miami. After that (and maybe even during), I’ll be following up with some more detailed information regarding their CMS. I’ll get a bit more into how certain things actually work, and what we’re doing to make it work to our advantage. In the mean time, their portfolio can give you an idea of what the system is capable of.

Update (08.04.21): If you are looking for additional support, be sure to either check out the dotCMS mailing list, or visit our newly established forum community. Also, expect new and improved documentation and support tools from the dotCMS development team around the 3Q of 2008.