A reader wrote to me the other day with an idea for creating a central place where any reader could contact any author with book-related questions. It would be a social media type idea along the lines of Facebook, Twitter, or LinkedIn, but with a book focus. The way this idea works is that a reader could leave a question on the central site and then the author would receive a notification through e-mail about the question. The question and its answer would remain public. That way, other readers with the same question would see the answer and not have to ask the author about it again.
This blog fulfills the idea that the reader has to a certain extent. When I receive e-mails from readers, I determine whether the question has enough interest to affect a large number of readers. When the question is better answered publicly, I put an answer up here, rather than answer it privately. Of course, there are times when a reader question needs and deserves a private answer. Using the blog approach does make it easier for me to handle some questions discretely, but nothing would keep me from including an e-mail address for that purpose in the book. The problem with this blog is that reader need to know to look here for answers. Even though I publish the URL for this blog in all of my books, readers still managed to miss it somehow and I get queries in e-mail about the availability of such a central knowledge store.
Wrox provides a centralized location for readers to exchange information of the sort that the reader mentioned, but it’s not as well known as the social media sites and I didn’t think to include the URL for it in my book (the publisher does include it as part of the Introduction). My experiences with Professional IronPython, Professional Windows 7 Development Guide, and C# Design and Development tell me that the concept is good, but reader participating is often poor. I actually get a lot more input on my blog.
I like the idea this reader has because it provides a social media type approach to a pressing need authors have to service reader requests for information. The problems are figuring out how to present the idea publicly, implement the idea in software, and then to make the site popular enough that it actually does what it’s supposed to do.
Of course, I’m always looking for input from you on making things work in a way that’s easy for you. What do you think about this concept? Is it possible to create such a site and have it become a success? Would you even frequent such a site? Let me know your thoughts on the matter at John@JohnMuellerBooks.com.