How about a sticky link in the top of this forum?
That would also make it easier for us to find/reference help topics within this forum.

Dom, why not start with RSD? It already includes up-to-date CSS/HTML, making it easier to ensure your site is cross-browser compatible. No need to go back and forth between 2 programs.

Bob,

I am one of those that would love to see a PDF help manual. For me it is difficult to dedicate half my screen to RSD and the other half to the help files. And then if I click on a link in the help file and then another link and ......

For me, just much much easier to get and print a pdf with a good contents and index. Old school I know, but for me that is how it works best.

Galen

+1 +1 +1
And there's nothing "old school" about providing a manual with a product.

1 +1 +1
And many of us come from the 'old school' anyway.

I'm wondering whether the seeming difference of opinion about whether a PDF manual is needed arises as follows. With many websites, the printing out of web pages is a nightmare, and some users may have assumed that this would be so with CoffeeCup online manuals, but that (unsurprisingly) is not so.

The RSD Resource Overview, RSD Resource Index, and the articles to which they refer, do print properly without the side margin items etc. It is therefore easy to print a manual from them without the need for conversion to PDF first.

Frank

I have almost every piece of software put out by CC. I'm addicted to their software. I buy it when I don't even need it. I think I need professional help.

Although I own most of their software I am not well versed in any of them. All the software is great and I enjoy the challenge of trying to learn them. When I first spotted CC and began using their products there were PDF help manuals.
A single click on the help button and I had a great manual in front of me, easy to search through, easy to study, easy to print.

I just don't like clicking help and going to the web-based system now in place. And, I don't think it would be very easy to try and go to each article and print it out and then try to piece it together in a manual. No table of contents, no index, no continuous page numbering, etc. Which articles should be included, which are specific to RSD, which are general in nature, etc??

Galen

Unfortunately, I have to agree with many of the users on here about the lack of a clean/concise '.pdf'-type of manual. DO NOT get me wrong...........I am appreciative for ANY help docs, links, articles, tutorials and the like, however, my user level is more or less in its infancy and I have been struggling through the online material. There are simply so many links to so many different articles that it gets confusing rather quickly. Thereby adding more confusion to the learning process.

I, too, (I'm afraid), am old school and prefer a static ".pdf" format with TOC and index for finding specific features quickly. The online support docs are simply painful to navigate through and by the time I find what I'm looking for............I've broken my train of thought on the project I'm trying to develop. I know, (or hope at least), this will abate once I get higher on the learning curve of the program(s), but is is extremely painful and discouraging at the moment. That is probably why you (CC people) are hearing so many remarks about it.

Online resources, (I think), makes it easier for CC people to keep things updated. It also keeps users coming back to your site; thereby helping you keep tabs on traffic and such; (which I'm sure is NOT the intent). However, resolution of this "manual issue" could be done with a ".pdf" manual and then just put out revisions when necessary. But wait.........it takes a great deal of work to put forth such a doc??!? Maybe, but is also takes a great deal of work to put together and refresh article after article.

I, for one, work in the electronics repair industry and rely on ".pdf"s all the time for acclimating to the many different types of equipment we work on. I am also notorious for keeping (and properly labeling to archive) service/help docs and software as it comes out. This permits staying up to date AND gives me something to fall back on when a new version of something is buggy; (cause we all know THAT never happens).

In an attempt to solve my CC support docs issue...............I have, literally, started my own index of terms, features and procedures which then link back to the particular article which helped. Then again...........when our roof leaked and the landlord would not fix it.........we built a completely separate sub-structure that, basically, aqueducted the incoming leakage back out of the building. A timely chore in and of itself, (and a nuisance), but we all do's what we gots ta do.

Please do not get me wrong.............I, too, am a big fan of CoffeeCup and have pretty close to most of their software; (albeit I use only a fraction of it.......at the moment). My point.........I'm not simply looking for a reason to throw stones. That being said, if you, (CoffeeCup people), are hearing the same complaint over and over again...........you might want to reassess. Not all people are born as lovers of CoffeCup and the problem seems to be turning some users away to other resources.

All imho, of course. </rant>

You can save the webpages to your pc.