Hi Victor, I'm a systems analyst with the City of Escondido, California, and the primary technical support person for our web sites. We are included in the first of the links you posted, but a more comprehensive list of our sites can be found in my own success stories thread. I'm not sure I agree that government is completely different than the private sector--we have many of the same user experience concerns (both internal and external), but I suppose one place we (happily) differ is that we have very little of the SEO concerns that plague commercial sites.

I'd be happy to answer any questions you may have about our sites and implementation.

Jamie

Okay, I see what you're saying. Luckily, our project was sort of a "bottom up" implementation. What I mean by that is we had a number of HTML sites that were functioning to everyone's satisfaction, but in the IT department we wanted to modernize our sites and decentralize some of the tedious editing chores. We had no budget for a project, so I went through and evaluated a good 6-8 open source project and mojoPortal won by a mile. We demoed our new site to department heads and the City Council, and they loved it, so it was full steam ahead after that.

I agree it can be difficult to get buy-in from decision makers who are already convinced that another solution is the better one, but I'm sure if you prepare a cost benefit analysis, and demo how easy mojoPortal is to maintain and operate, you'll be able to get people onto your side.

I don't know what specific security requirements you have, but I've always been very impressed by mojoPortal's security structure. In fact, I'd say that it's been designed with security as the topmost concern, and potentially useful features have been rejected by Joe because they might compromise security. I mean things like the ability to edit the config files for the site, through an interface within the site.

Jamie

Hi Victor. I'm sorry but I don't understand what these regulatory requirements are. Are the regulations posted online anywhere in English so I can take a look at them?

Jamie

Okay, that makes sense. I guess it depends on the definition of that audit trail, then. We aren't required to keep one ourselves, but we did turn on Content Version History for HTML features, and enforced it for all sites. In our case this was to give us an "undo" capability in case of an editing mistake. But if you did that, then at least for HTML changes you could write a SQL query to generate a list of all the edits made within a time frame. I believe Joe has it on his to-do list to expand the number of features that support content versioning (blog entries would be an obvious candidate, for instance), but I don't know where that stands in the development queue.

I hope that helps.

Jamie