In case you missed it, Marqui’s paying me for my time and opinions… I feel more like a consultant in my interactions so far. I have yet to write about suggested topics such as the David Suzuki Foundation’s use of Marqui, etc, and instead have been approaching this as a design problem. I’m looking for UI interface issues, problems with the feature set, technology issues, etc.
As an aside, wouldn’t it be neat if the calendar in the CMS could be exported in iCal format, just for pure giggles?
Anyhow, I recieved the following message from Thierry of Marqui (by way of Marc) today, and my response follows.
We are still trying to figure out how clearly position ourselves with more technical people. Yes, it’s true, the tool is programmed with ASP, but the web properties you build with Marqui are completely platform and code
We are the only CMS that can be used as a development platform for both .NET & J2EE. We have clients managing their Java on UNIX, PHP on Windows, CFM, XML, XHTML, even companies producing exclusively Word documents to a file server, etc, etc.
This is why our partners love us so much. There are NO restrictions to the code or platform you can use.
The problem is that this is not clearly defined – and I wouldn’t expect you to find that out just by looking at the tool (I know I wouldn’t figure it out!).
So now that we know that, we will try to bring this forward into our messaging – thanks to your input! ;-) This is why this blogosphere program can really work for us – real time feedback! So I would invite you to say
more things like this – whatever bothers you, we want to know about it!
Here’s how some of our technical resources talk about it:
- The Marqui application will publish your web content to any hosting server (regardless of O/S), anywhere, as long as it’s connected and accessible via FTP over the internet. We can bomb-proof & secure this connection in a number of different ways.
- The Marqui application keeps a copy of your content here (on our servers) so that any time you access the Marqui application, you can add/modify/create/delete/play with your content. You access the Marqui application and our copy of your web content using a Web Browser (at this time, preferably Internet Explorer).
- We then publish (by FTP) your content to the final desired hosting server of your choice. At any time, if you were to decide to stop using the Marqui application, you would have ALL of your web pages available to you on your hosting server. This content could then be modified/created/deleted by any other means of your choice.
- Marqui can publish to up to six different servers, running different environments such as Linux, Windows, MAC OS, etc. This feature is especially handy for clustered or load balanced environments, or to publish the same
content to different web properties.
- The same content entered once from all languages can be presented in up to seven different output formats such as web, Print, PDA or XML ready, to one or all of the six different servers.
- Marqui can publish the directory of your web property to an unlimited version of languages, all customized to meet your specific needs.
- Publishing flat files ? or static HTML ? to the live web server offers great advantages over the traditional 2, 3, or ‘n’ tier database systems currently available on the market.
- No additional hardware or software is required, no application, complex firewall or database to configure on your live web server. It increases the web server speed (no pulling from a slow database) displaying pages for visitors a lot quicker (using kernel caching)
- Improve your web marketing initiatives: search engine robots cannot pick up data from databases without a costly engine. With flat files residing on the web server, search engines are able to retrieve the entire directory with all the pages associated with it.
- Marqui delivers this robust Communication Management System (CMS) subscription over the Internet. When users collaborate on tasks, all communications are encrypted and stored in Marqui’s database, making it virtually impossible for any unauthorized third party to read, access or modify that content.
- Separate databases are created to manage distinct web Properties through Marqui Manager. Unique client codes corresponding to each web Property are assigned to each database. Marqui manages multiple databases while maintaining database independence.
- A web server can also be running other e-commerce, CRM, or custom applications, while Marqui publishes around these applications, without requiring special integration. Our web service engine will also allow full integration with any third party application, providing a web based interface to many leading technologies not currently offering this functionality (SAP, Pivotal, Siebel, etc.).
- Marqui is an open application, allowing all programming languages (ASP, XML, WML, CFM, HTML, etc.), and any kind of HTML authoring tool.
I appreciate that the system can integrate on the SERVER end of things transparently, generating content and uploading it to pretty much anything anywhere….
My problem with the technology is a bit more basic than that, and it’s a spot where technology does get in the way. I’ve mentioned this at http://foo.ca/wp/index.php?p=7122 and it’s kind of a technical sticking point. It’s one of the items that an IT person can bring up in the sales process that could theoretically stop implementation in security concious locations.
“This is why our partners love us so much. There are NO restrictions to the code or platform you can use.”
On the server, this may be true, but is there ANY timeline for enabling full client access transparently from any browser? Say an optional Java or Flash interface that could be used from any client platform? With the company I’m picturing using this product, the developers would be involved in content production and release, and they’re running on a variety of OS. Some Linux, some Windows, and some OSX. That means I’m dealing with Safari, Opera and Firefox 80-90% of the time…
“We then publish (by FTP) your content to the final desired hosting server of your choice. At any time, if you were to decide to stop using the Marqui”
Can this be setup as, say, an rsync connection over ssh? Some of my servers are pretty heavily locked down. Is there a specific IP address that I should allow to penetrate my firewalls, or a known range of them? These are pretty implementation specific, I suppose, but they’d be questions that my developers or I might ask during the
I included my number, should Thierry wish to call me directly rather than contact via email, or blog. Some people are old-school that way and like to talk to humans…