TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
That's a great link. Thanks for that link. Neat that one of the founders of
WhatFix responded as "The first competitor to WalkMe".
I just remembered, our team did localize WhatFix content, but the
localization team warned that many translations added 30% to the content,
so the authors had to consider that when spacing the balloons.
I think my problem was the lack of an actual content-management mechanism
that lived outside the WhatFix interface. For example, if you wanted to
produce content before your app was ready. Or, when sending content for
translations, there wasn't an automated way to isolate only the content
Another consideration is that WalkMe is closely tied to Salesforce. That
might provide valuable benefit if Salesforce exists in your process
On Wed, Apr 11, 2018 at 4:32 PM, Monique Semp <monique -dot- semp -at- earthlink -dot- net>
> Here're links to a few more alternatives and listicles of alternatives:
> * particularly interesting because the question included reference to
> multi-lingual walk-throughs - https://www.quora.com/What-
> * Toonimo, often mentioned as an alternative - https://www.toonimo.com/
> * And Appcues - https://www.appcues.com/
> * Blog post touting Whatfix - https://blog.whatfix.com/best-
> * Listicle from 2016 - https://www.iridize.com/blog/
> Seeing this thread has me thinking that my current team might really like
> this for a quick way to document alpha/beta-stage features that we know
> will ultimately quite different. The increasing frequency of
> try-em-and-change-or-drop-em software work is causing a lack of docs
> because nobody wants to take the time/effort for throw-away docs. So maybe
> the fact that these walk throughs of course aren't practical to maintain
> for many reasons -- in fact, all the issues with screenshots, only vastly
> worse -- just doesn't matter if they're so easy to create.
> Thanks for the discussion!
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com