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.
Here're links to a few more alternatives and listicles of alternatives:
* particularly interesting because the question included reference to
multi-lingual walk-throughs -
[1]https://www.quora.com/What-are-the-alternatives-to-WalkMe-I-want-to-
add-multi-lingual-walk-thrus-to-web-apps
* Toonimo, often mentioned as an alternative -
[2]https://www.toonimo.com/
* And Appcues - [3]https://www.appcues.com/
* Blog post touting Whatfix -
[4]https://blog.whatfix.com/best-walkme-alternatives-whatfix/
* Listicle from 2016 -
[5]https://www.iridize.com/blog/top-walkme-alternatives-in-2016/
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!
-Monique
