Galen Garretson wrote:
This thread really does bring up the issue for the need for a cohesive help manual. I am just now trying to learn RSD. I find myself getting very frustrated going to the CC website and trying to look through all the help articles to find the answer to my questions. So, I go back to RSD and just try to figure it out. I'm getting things done, but it is sure hit and miss.
Come on CC, you have great software. Now make a great user manual. Or, put the issue to rest and say "Yes, we're going to do it" or "No, we are not going to do it".
Thanks,
Galen
Galen, give us an example of what you feel you need instructions for? Don't be generic and say "well everything"
Do you want just cut basic information that explains each and every feature (Class, ID, Change Tab, Apply To, State, Width, Max-Width, Min-width) or do you want something explained that is focused on a particular task (Flexbox, Navigation, etc.)? If it is task specific, we do have many articles that cover a wide variety of things already so if we are missing one, let us know what you think needs to be expanded upon.
To us, it seems a waste of time to explain what a Class or ID is as these are common terms that you can find the definition for within many basic HTML/CSS for beginners books or resources on the web. We also know from painful experience that no matter how much documentation we create, there will always be a segment of users that still will not read any of it. So if anyone has specific (be extremely detailed in what you ask for) articles or how-to's that are lacking, outline them here and we will see what we can do. Again, be very detailed so that we can learn what exactly we should be improving up.
Thanks! :-)