The bottom line is that I really think we’re on the right track with ActionContent. The biggest indication of this for me is that I didn’t see one thing this weekend that made me go, “Oh wow, we really have to have that. How have we gotten by without it?” ActionContent does what it does very well, and I don’t think a shrink-wrapped system would do any better at 90% of what we’re doing.
However, there is 10% worth of bells and whistles – some very elementary, some debatable – that we should probably think about putting into the system. I’m very interested in some of the Library Services I mentioned earlier. As use on the Intranet expands, we’re going to need things like version control and rollback.
Also, the current system could use some work in the usability department. I say this not from any content management seminar, but from several of the usability workshops I went to. The admin side of ActionContent is very good (and development-free, thanks to Chris), but we’re Neanderthal Web developers. Sure, it makes sense to us, but we have sloped foreheads and our arms drag on the ground when we walk, so we’re not like the average Joe. The Intranet is going push content publishing more and more into the hands of some very non-Web experienced people, and the current interface may send them into shock.
From what I’ve learned, I also think that the whole system would be bound together and served quite well by a first-rate search engine (man, that T-shirt the FastSearch people gave me is really going to pay off for them…). I think a search engine would bind the entire Intranet together – content management, file shares, message boards, current HTML, etc.
As the search engine takes off, META tags and keywords are going to be very important, so it would help to let users enter things like that.
Finally, do we have any collaboration aspects in ActionContent? Primarily, could a content publisher tell someone, “Hey, go look at this content and tell me if you think it’s ready to go.”? If not, this would be nice to have as well.
In the end, I think we need to scale back of “expectation of talent” we have for the average ActionContent user. As far the Intranet is concerned, this user is not going to have any development experience, may not have much Web experience in general, and may even be something of a computer novice. Additionally, this user is going to be prone to make mistakes that we need to be able to recover from, and will likely make content development and publishing more of a team-based, collaborative effort than we’re used to. We have to be able to support these people.