The were specific types of crashes already moved to separate articles, but because of the generic nature of the issue, the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article was still bloated. Articles that are brief and address a specific question tend to get the highest ratings.
And so we'd like to change the way that article helps users. By teaching users to find their crash signature, we can create a separate article for each crash signature, with that signature prominent in the article text. Troubleshoot Firefox crashes (closing or quitting unexpectedly) would start by introducing users to about:crashes, and how to find the signature in the online report. Then tell users to search the knowledge base for that crash signature (maybe link to all of them from within the article).
One of our most common issues is Firefox crashing, and the [[Firefox crashes]] article already has a lot of information in it, covering various different causes. The article still has a very low [/tiki-poll_results.php?locale=en-US&list=y&pollId=237 Did this article solve a problem you had with Firefox? rating], and a below average [/tiki-poll_results.php?locale=en-US&list=y&pollId=2547 Was this article easy to understand? rating].
The were specific types of crashes already moved to separate articles, but because of the generic nature of the issue, the [[Firefox crashes]] article was still bloated. Articles that are brief and address a specific question tend to get the highest ratings.
And so we'd like to change the way that article helps users. By teaching users to find their crash signature, we can create a separate article for each crash signature, with that signature prominent in the article text. [[Firefox crashes]] would start by introducing users to about:crashes, and how to find the signature in the online report. Then tell users to search the knowledge base for that crash signature (maybe link to all of them from within the article).
Chris, the Firefox crashes article is ABSOLUTELY the first article that's going to need a PERFECT screencast that ANYONE can follow.
Can you do that? :P
As I've seen people still grab the wrong information when told to visit about:crashes and some people frequently go, where do I put that? Well I'm tried of giving long explanations on grabbing a crash report. I'm pointing to the screencast as soon as you up it.
Chris, the Firefox crashes article is ABSOLUTELY the first article that's going to need a PERFECT screencast that ANYONE can follow.
Can you do that? :P
As I've seen people still grab the wrong information when told to visit about:crashes and some people frequently go, where do I put that? Well I'm tried of giving long explanations on grabbing a crash report. I'm pointing to the screencast as soon as you up it.
I can do anything, if i put my mind to it. :-)
I think the biggest obstacle is that we don't know how many users know how to copy/paste text. We'll probably have a list of links.
I can do anything, if i put my mind to it. :-)
I think the biggest obstacle is that we don't know how many users know how to copy/paste text. We'll probably have a list of links.
That's not a big deal. If they're pasting to livechat or forums, the contributors can deal and sumobot can linkify crashIds so if you need it linkified and you're lazy just paste what you got into IRC and sumobot will parse and do the work.
The point is if they get the crash signature, they should be able to search on that.
That's not a big deal. If they're pasting to livechat or forums, the contributors can deal and sumobot can linkify crashIds so if you need it linkified and you're lazy just paste what you got into IRC and sumobot will parse and do the work.
The point is if they get the crash signature, they should be able to search on that.
