Take the 2-minute tour ×
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

When I discover an error or omission in the SFDC Developer Doc, I go to the section at the bottom of the page:

enter image description here

and fill out the "yes, except" or "no" feedback form. My belief is that since I rely on the doc, where it is incorrect or missing some clarification, that others should benefit from ever-improving documentation.

My question is: Does anyone ever actually read and act on the doc feedback? Is there a better channel to use? I can imagine that a tech writer has to reproduce the use case, consult with an engineer, go through approvals/QA and that this might be all too much bother given higher value docs to be produced for new features.

share|improve this question
4  
I've done this a few times but have never received any feedback to the email address I supplied and have never had the willpower to check if a change was made in a later version of the documentation. So I will be interested to see what others have to say here. –  Keith C Mar 27 at 18:10
    
I, too, have never received any feedback to the email address supplied by me on the feedback form. Not even a 'thanks' –  crop1645 Mar 27 at 21:27
add comment

2 Answers 2

up vote 9 down vote accepted

These reports go directly to the doc writer team, and by far is the quickest & easiest way to give feedback and get improvements in the doc, and is at least as effective as getting bugs logged in the internal system. [I have access to the internal bug system, but still report doc issues via this form]

share|improve this answer
3  
Could you share with the doc team that they would probably get more feedback if they responded to people? –  Keith C Mar 28 at 10:07
    
Yes, will pass this along. –  superfell Mar 28 at 14:42
add comment

I'm a Principal Technical Writer for salesforce.com, and it's true, we do look at all comments and file bugs on the doc issues that are raised. Technical writers are actually hungry for customer feedback.

Please keep commenting. As others have pointed out, it may take a bit of time to receive a comment, research it, make the change and release it, but there's nothing more important to us than hearing from our customers.

share|improve this answer
2  
As Keith mentioned on Simon's answer - more responses to those of us using the form might be helpful. Just a "thanks for the feedback, we've accepted it and it should be making it's way into future docs" or "we're investigating the details with R&D" makes people feel much more involved. –  ca_peterson Mar 28 at 18:57
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.