An overview of configuration options would be nice :-)

Requirement: use native help mechanisms (Windows .HLP versus Gnome
Scrollkeeper?) on each platform.

If you know nothing about break-software, wr is very hard to understand. When
you start it, a window pops up with some icons whos meaning is not immediately
clear, and some progess-bar like widgets in all kinds of rainbow colors and some
digits counting down.

An overview of what these widgets mean would be helpful, as well as an
explanation of the ideas behind them.

Currently, wr is only usable if you are familiar with wp or some such program.
If we're going to attract new users, this situation should be improved.

I would recommend not diving into the details of native help mechanisms right
now, but instead generate some content first (for example web-based), and then
convert it to some more desirable format later.

The native help mechanisms are not the problem here. The bulk of the work is
writing the documentation itself. And, if the documentation is written in
docbook it can be easily converted to HTML and other (online help) formats. 

So, regardless of what type of documentation your are going to write, be it for
the web or whatever, if you do so in docbook, adding online help using native
mechanisms is relatively easy to do.

Oh, I noticed your set the component from Core to Gui-Gtkmm. Both are wrong
actually, we need a "Gui" component.

Let's be honest, this is not going to happen any time soon...