At the dinner table the other night, my older son asked me what Marqui was, and whether I used it. I told him I didn't, and he asked if I was endorsing it. I said I wasn't, that I was just writing about it. He wanted to know how that was different. My younger son piped up and said "Because she can say that they suck if she wants to!"
Yes, I could. I could write for three months (well, two more months) about how much I hate Marqui. But since I haven't used it yet, it's tough for me to say anything bad about them. And I can't really complain about the terms of my agreement with them--I'm able to clearly separate sponsored content from non-sponsored content, and there are no restrictions on what I can write.
Thus far, I've written pretty general material about the blogosphere program Marqui is running, and about what CMS programs do, generally. Tonight I'll start talking about Marqui more specifically.
Marqui bills itself as a "communication" (not content) management system. The content that it lets you manage, however, is very focused on communication. On their site, they say:
You enter a space online that lets you manage your website, brochures, events, e-mail campaigns, newsletters, grant proposals, press releases, donor outreach — any kind of communication. You input information once, Marqui will output to all sorts of formats. Input once, output many — that's how it works.
I don't know about you, but that sounds a lot like my department's information needs. And right now, we do a lousy job of managing all that content. We duplicate things in so many places--catalogs, web sites, email messages, etc. Consolidating content, managing workflow, and reducing duplication are needs that probably aren't unique to my environment.
Marqui is a hosted environment, rather than a package you install on your own servers. They call it "Software as a Service." The cost ranges from $199/month to $499/month, depending on the scale of your operations. While that may sound like a lot, compared to the tens or even hundreds of thousands of dollars that it costs to license some high-end, enterprise-level CMS packages it's not really all that much.
That's it for today's hosted installment (a few minutes past the end-of-the month deadline, alas, but since most of it was written in January, I'm counting this as a January post!).