Marqui - Content Management in Vancouver and Blogging for Money
Marc Canter has gotten quite the storm of controversy about paying bloggers to...blog. Of course, Marc won't get any respect until, say, Microsoft does it.
Roland and I met with Marc Tuesday night to go over some Bryght business (this, this, and this, if you must know). Marc also gave us a preview of the new Marqui (nee MaestroCMS) demo. Marqui has some great workflow features, they output to multiple formats, and they even have RSS feeds in their newsroom now.
Would reviewing a CMS make sense for my blog? Absolutely.
Yes, my business might be considered a competitor, but I've already been thinking how the two systems could work together. Let Marqui handle the complicated workflow of larger corporations and a mass of static content. Let Bryght handle your community site, developer forums, or other highly-dynamic sections of your web presence.
Heck -- this post might be my first entry in a paycheque from Marqui. (Disclaimer: I'm not being paid to post this right now)
In any case, congratulations to Marc and Marqui. It's great to see another Vancouver company doing really interesting work, and succeeding.
Similar
Comments
a say who ? a what ? CMS is a deep topic ; MS IIS ?!
The linked storm of controversy @ Marqui's site is a difficult read -- I think I made need some more context than what is present here or there . Susan Mernit's post , link titled Microsoft does it is more literate .
I would be interested in your review of Marqui , though it takes a lot of time and energy to dig into these things . In the saturated CMS market , I wonder what differentiates Marqui . Looking at Marqui's client list , it seems that they have excellent regional marketing !
I did previosly note with some surprise that www.davidsuzuki.org appears to be on Microsoft-IIS/5.0 . This also appears to be the case for www.marqui.com .
Marqui doesn't host
They have done a good job of setting up their business in such a manner that they host all the CMS tools, but then publish the files to the remote site. This has the downside of being completely static content (well, unless you integrate ASP/PHP with the templates, much like MovableType), but the upside that there is no dependency (or liability) on Marqui to be up in order for client websites to be functioning.