Seth Dillingham has a funny post here about users who ask him to configure Conversant in weird ways,
A Conversant user recently asked me to custom-configure one of his sites, because he wants to do something that isn’t available via the web-based configuration.
Why not? Because we never saw anybody wanting to do this. We’ve never done it, never tested it.
I set it up for him, but I’m still experiencing heart palpitations.
I know what he means, because I’m the one who requested the odd custom configuration. So far, its worked incredibly well. In a couple months I’ll be able to show off the cool things I’m doing thanks to this bit of wizardry.
But what it really does is speak to just how well Seth’s developed Conversant. A lot of software tends to produce very frustrating roadblocks. Its great if you want to do things the exact same way the developer does them, but start deviating from that plan or start asking “what if I mixed feature A and feature B” together, and most of the time you’re out of luck.
Conversant, on the other hand, does an excellent job of taking a wide variety of basic building blocks and then letting the user mix and match them in pretty much anyway he or she wants. There have been a handful of times where I’ve done something in Conversant and it worked even though Seth said he hadn’t thought of using the feature in that way. When you can do things with software that the developers never intended or thought of, you’ve got an extremely well-done piece of software.
And that’s a great way to describe Conversant.