@kaykay @evan @sam not sure which one of you could help me with this. I am currently working on some "stuff" that I think may have a place on Wiki's. I was wondering what the percentage of views on Wiki's is compared to Answers and Guides. I know it's a bit of an odd one, but so it the OP...;-)
Hey OT! We don't get a ton of natural traffic to Wiki pages, most of our traffic is google-driven straight to answers.
Wikis include device pages, tool pages, and troubleshooting pages, but they're not usually first hits on google like Answers pages are. However! Wikis get a good number of hits when linked in Answers, for example the water damage wiki. So as far as where to put a thing, if it doesn't have many photos, and needs a lot of text, it should probably live in a Wiki and get cross-linked to as many guides, troubleshooting wikis, and answers as is logical.
And you can always scroll to the bottom of answers posts, guides, and wikis to see the individual view counts for that page.
Also, OP is my favorite kind of odd :D
5 Comments:
@sam thank you Ma'am. I was thinking about our basic troubleshooting Wiki's we've discussed on here before. Looks to me like Wiki's is somewhat underutilized. I think we need to think next gen fixer and have some basic "guides". I thought it would be great if there would be easy access to those vs. going through Answers. Those "guides" would probably have plenty of text and images. I am thinking about Ideas for guides...I'd like to bounce some ideas by @refectio . Would you recommend to post those future works as Wiki's or as Guides?
I greatly appreciate you, your answers and your willingness to always help out :-)
by oldturkey03
I agree with @oldturkey03 on the usefulness of Wikis to note certain information. I've used the Wikis to differentiate the Xbone 1537 and 1697 controllers and note hardware design issues in laptops like my Dell E6540 I have noticed over the years.
I think we can put basic information like the variations between the revised and original controller (along with that has not changed) and even information on "unbricking" the device in question if a firmware update was interrupted. I have also used it for laptop Device pages to point out known hardware flaws, like subpar cooling on a laptop that can cause issues if you buy the quad core model, but may not be an issue on the dual core model.
by Nick
Wikis are great for lots of things, and are certainly easier to manage than guides, so that's a good endorsement for just making a simple article. Nick's right about device page edits, too.
I think our team tends to find some content lends itself to the step-by-step approach a bit more. To use Minho's examples, "How do I test a capacitor" may be best as a guide, akin to this capacitor discharge guide, while more general content like "how to read schematics" would be a great wiki resource. I think of wikis as less step-by-step direction and more instructional content. Another difference is that guides make tool and part listing much easier, and can be prominently displayed on a single device page, where wikis can be linked to and apply to many devices.
I would recommend looking at the Skills category to see some general guide examples.
@sam you were supposed to make this easy for me : ) and just tell me what to do:-)) Skills it will be. I like that and think it will work great for our plans. Thanks Sam!
by oldturkey03
Well, you know that saying about teaching a guy to struggle and he'll be good at catching fish, or something...
If you do have more questions, I'll see if I can give more specific answers ;)
272 
103 
7