Creating Your Troubleshooting Page
Your troubleshooting information will appear on a wiki page with specific formatting guidelines.
The basic layout of each troubleshooting topic should resemble the following format:
- Heading phrased as a user-observed symptom
- Description of the symptom in italicized text
- Subheading phrased as a possible underlying cause
- Solution of how to complete the repair
When formatted correctly on your wiki page, it will look like this:
When creating your troubleshooting page, it's best if only one team member edits the page at a time. If more than one person attempts to make changes simultaneously, they may unknowingly overwrite each other's work.
To create a troubleshooting page:
- Click here to start a new page.
- Select "Wiki" from the list of options.
- Enter "[Your Device Name] Troubleshooting" into the title field.
- Do NOT include the device type or generic terms such as “laptop,” “cell phone,” etc.
- If your device was provided by iFixit, copy the name directly from the white iFixit label on the device.
- For all other devices, write the name exactly as it appears on the manufacturer's website or in the device's official documentation. If your device is known by more than one official name, stick with the most common one (Google Trends can be helpful here). If you're not sure, drop us an email at techwriting[at]ifixit[dot]com!
- Be sure to use correct spelling, capitalization, and spacing when creating your troubleshooting page. For instance, the 's' in Cyber-shot is not capitalized, while the 's' in PowerShot is.
Below is a snippet of the Lenovo Essential G560 troubleshooting page source code. This should give you an idea of how it's formatted. You can copy/paste the code into a new troubleshooting page, and then just change the text as you see fit.
== Audio Distortion ==
''You have trouble listening to sounds on your computer.''
=== Loose Headphone Jack ===
Test audio through the computer speakers, then test it using headphones. If the audio is only distorted while listening via headphones, the audio jack or the headphones themselves may be faulty. Audio that cuts in and out is often a sign of a loose audio jack, so make sure the audio jack is fully inserted in the computer.
=== Faulty Driver ===
If the audio sound is distorted when listening through the laptop’s speakers, the audio driver may be corrupt. Search for [http://support.lenovo.com/en_US/landing.page?qpq=g560#|Lenovo G560]. Click “Lenovo G560 Notebook,” then click “Drivers & Software.” Click the “Audio” tab and select and download the appropriate driver. Go to Control Panel -> Device Manager -> Sound Controllers. Click on your sound card and click “Update driver.” Select your updated driver, then restart the computer.
== Failure to Read CD's and DVD's ==
''Your Lenovo G560 will not read any CD's or DVD's.''
=== Broken/Defective Optical Drive ===
If your Lenovo G560 optical drive does not open or does not read CD's or DVD's, the optical drive may be broken and [guide|12751|needs to be replaced].
(Enclosing text in double equals signs creates a heading, and triple equals signs creates a subheading. To italicize text, add two single apostrophes around it ( ' ' TEXT ' ' ). To bold text, add three single apostrophes.)
Copying the above and just changing the text will help ensure that your formatting comes out perfectly, but you can also use the built-in Word-style controls to make formatting changes:
The rest of your troubleshooting page should follow the same format for headings and subheadings. (While editing your page, you’ll also find a yellow "Help" icon that links to our wiki formatting page, which explains all the formatting options available to you.)
When you're finished, be sure to check the box labeled "Show table of contents?" at the top of the Edit page. This automatically creates a linked table of contents on the left side of your page using the headings and subheadings you've just defined.
Princess Leia: I hope you know what you're doing.
Han Solo: Yeah, me too.
Do you know what you’re doing?
Better review those technical readouts of the battle station—or at least the guidelines in the milestone—before you find your grade plummeting into the Great Pit of Carkoon to be eaten by a sarlacc. Email us at techwriting[at]ifixit[dot]com when you have a finalized draft of your troubleshooting page, and we’ll let you know when you’re ready to make a run on the Death Star, or, Milestone 2.