Perhaps this thought might be an overkill but the coder in me can't stop thinking about automating CD. Something like a COM Object Model would be sweet! But I do understand that this may not be in the big picture view of where CD is going.
Given the Access backing of CD, of course, some of that would be trivial. For example, anyone could write a COM object named Stories that presented a collection of Story objects that corresponded to the items in the CD tree. You could add, delete, edit items that way if you wanted to. But the core publish/preview functionality is in the CD code, and that isn't exposed (at least, I think it isn't).
You've read my mind completely! Basically I would like to use CityDesk on a server. Here's my concept of it:
Hmm. And then they would charge thousands of dollars for it, and it would be the same as Interwoven or e-Grail or Vignette or one of the other big players (okay, e-Grail isn't that big). How would they distinguish themselves from the others?
I understand what you're saying here but I wasn't invisioning a huge server software product. Just by exposing a few features to something like VBScript would be killer. It was just an idea that I saw potiential in.
The nice thing about this would be to turn CD into a publish-from-anywhere engine. If we had a CityDesk.Publish method that we could call via an API, this could be implemented today.
One thing I'd love to do is to be able to let people enter articles into CityDesk via a web interface for immediate publication on the site. Also, if you could reliably enter an article with a "Do Not Publish Before' date and have it publish w/o user intervention on that day...
Fog Creek Home