Dr. Explain Reviews

This truly is the real solution, just as described as doctor is not just for name sake

I have to say, this is truly impressive and performs very well. In fact, rather than finding anything to dislike, I actually feel a bit envious of the developer.

Dr. Explain is a help authoring tool created to address the challenges of producing, updating, and publishing high-quality software user documentation in a fast and efficient manner.

Dr. Explain is intuitive and easy to use and install. I really appreciate how seamless it was to convert a competitor’s compiled helpfile to a Dr. Explain helpfile (no additional typing or cutting and pasting needed). I also like being able to easily create an online html helpfile with free Tiwri hosting using Dr. Explain. Creating and integrating context sensitive help into Delphi code was simple too. In addition, it was not a problem to switch the license and project to a new computer.

In summary I bought Dr. Explain because I need a helpfile compiler that provide online helpfiles with hosting and context sensitive help and it worked extremely well.

The free Tiwri hosting requires monthly reconfirmation and you only get a 2- or 3-day window to do this. I should not really complain since it is free, though. Otherwise I have not had any issues yet.

The thing I like most about Dr. Explain is about the functionality that allows us to create numbered steps/stages on an image explaining a particular function of a software. That is; using Dr. Explain we can capture image (screenshot) of a particular function of the software and then number each step on the screenshot accordingly. This can greatly help a new software user to clearly see the steps/stages of how to use a software and go through it effectively.

I don't think I dislike anything about Dr. Explain as everything works out fine to me. Particlarly, the layout and design seems to fit perfectly well to a technical writer who might be writing a user guide for a software because it have everything you might need to write a good software user guide document.

I highly recommend you to use Dr. Explain to write your software user guide because of its graphics display. Particularly, the numbered steps on the screen capture of a particular feature of your software system because it gives a good and clear layout and display of different steps/stages of a software feature.

I am using Dr. Explain to write software user manuals. Nowadays Software and digital products are now becomming very important part of our digital world and their usage has increase as well, so tools such as Dr. Explain can help us software and digital product developers to write good user guides for our products to be used by our clients and customers. A Walk Through Review On Dr.

We had a CHM file from an obsolete system, and Dr Explain was the best app we could find to import that and turn it into an editable format.

Copying and pasting content from various other sources is easy, so we can publish an article in our internal newsletter, and also include the same content in our Help file without having to muck about with a lot of reformatting.

One feature I like most is the ability to save in multiple formats such as HTML and PDF and have it be easy to use. I didn't want to spend a lot of time learning a new piece of software so fortunately Dr Explain is intuitive enough for me to get started with little need to look at or review documentation.

I'm not sure I've fully investigated the customization options to give our documentation its own look and feel. Perhaps this could be easier or perhaps I'm not looking for the instructions on howto do this.

It's a really good option for affordable documentation software for a small business like ours.

Our goal was to overhaul our documentation on something more powerful and effective than MS Word and we were able to achieve that. In particular, we wanted to get HTML-based documentation that we could manage and control on our own, and we're able to do that in a much easier fashion with Dr Explain.

Well implementend node-based authoring. HTML 5 and chm-support. WHYSIG for chm, pdf, hmtl.

Good callout designer with many options, though sometimes complicated. You can do your own callout sets, like choosing colours and using own icons, but it takes some practise. Easy to learn, easier to master than Word. Good, useable chm output which is real benefit seldom seen. Stable, good support.

Generally, good and reduced feauture set, compared to e.g.Word or Framemaker.

More callout sets included would help. A conservative callout set would be great (decent numbers in circles). PDF output is a bit simple, RTF-only Word import lacks formatting options, a bit. Dr. Explain could advance here. Please implement .docx- export! I would very much like templates for tables.

Simplicity, versatility, and power are the major strengths of the software.

Some shortcomings related to the customization of the layout (link color, ...)

We can now write personalized user manuals for our clients.

I use Dr. Explain for quality system documentation. The tool is simple to use and offers a host of very useful features. My favorite: the ability to generate a website and publish it on tiwri. Support: excellent as well: competent, fast, and pleasant. Bravo!

rien ! le logiciel est vraiment utile

Quality system documentation, process documentation, etc. Dr.

The easy to use and WYSIWYG interface of the platform

The output format covers all what we need

Automatical creation of TOC

Automatic creation of "search"

The screen capture feature that do all the job for me (automatic capture and analysis of the application controls, insertion into the doc, insertion of the annotations, auto TOC,...). I love it!

The collaboration feature that needs you to have Dr Explain installed on your workstation to use it. I would praise a full web application to generate help the same way.

Really worth a try! Simple and easy (and I am not a tech guy)!

I work at a medium non profit organization of the social sector. My main job is financial but I was invited to develop an integrated software application to help us manager more effectively our grants and our working force. When the development was finished, I needed to provide our users with documentation and help. I started taking screenshots of the application, copying and pasting them into a word document, writing the contents of the help, rearranging the TOC,... All this manually! The final help product was delivered on PDF format and send to our users by email. As the application was continuously updated, I needed to start all the process each month, over and over again. Finally, this started to keep away from my financial job.