MTRes: Great for Dumb Fiddly Crap and Frequent Mistakes, Lacking in Weird Edge Cases
August 04, 2017

MTRes: Great for Dumb Fiddly Crap and Frequent Mistakes, Lacking in Weird Edge Cases

Christopher Ryan | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Software Version

MindTouch Responsive

Overall Satisfaction with MindTouch

We use Mindtouch for client-facing platform documentation and release notes. While the whole organization has access, this means primarily that client-facing functions (Support, Success, Services) are the internal users of our Mindtouch instances.
  • Content reuse across articles and dynamically updating articles based on linked content.
  • Maintaining linked structures despite article name and structure changes.
  • Anchor implementation.
  • Solid WYSIWYG editor.
  • Multilingual content without cross-instance SSO and a special config would be great (I know it EXISTS, it's just, a big undertaking for a couple reasons on our setup).
  • Better visualization for instance architecture/article hierarchy would also be super.
  • More robust user...usage? statistics and tracking, without having custom reports run.
  • Increased product adoption.
  • Greater ticket deflection rates.
  • Less Success team time spent on experimentation on how to perform basic functions that have since been documented.
It's great if you want to put together some articles that you're probably going to have to rename, relink, or otherwise fiddle with after the fact. It's less-great if you're trying to maintain multi-lingual instances with easy interlinking of instanced content (but really, nobody IS good at that, so).