Site Navigation

Your Account

Choose Language

Checklist ¶ 

  • Did you sign up for an iFixit account using your school email address?
  • Did you join a student team?
  • Did you make a profile?
  • Do you know how to use milestone pages?
  • Did you choose a device that is not already documented on iFixit for your project?
  • Did you email a .PDF of your proposal to techwriting[at]ifixit[dot]com?
    • Does your proposal have all the requirements listed?
    • Does your proposal include the correct header?

Email Us When... ¶ 

...you have a proposal. You must email us with a proposal, even if it is informal. Proposals allow us to give you the necessary privileges to work on the site without problems. Email your proposal in .PDF format to techwriting[at]ifixit[dot]com. Include your team tag and device in the email's Subject field, as well as a brief message in the email body. (It's a nice professional touch—and a general courtesy—to not send a blank email with an attachment.) Don't forget to CC your team!

Join a Team ¶ 

1. Click here to add yourself to a team.

  • Even if you are working alone, you need to be on a team. Being on a team, even a team by yourself, gives you student privileges that allow you to complete your work.
    • Use your name and school email when signing up for the account.
    • Make sure to select the appropriate information from the drop-down menus. If you add yourself to the wrong team, just click "Leave my team" and try again.
    • Team tags follow this format: School-ProfessorLastName-T#S#G#. For example, if you are attending Cal Poly in Fall 2014, in section 4 of Dr. Jon Doe's class, assigned to group 7, your team tag will be: CPSU-DOE-F14S4G7.

2. Go to your profile and add an avatar.

  • You can click on your avatar in the top right corner to view your profile. On your profile page you'll see all the guides you've created.
    • On the same page, click the team tag below your avatar to view a list of your team members and your team's activity.
    • You’ll find a link to the Student Roadmap page below your team tag, so you can easily access the page from your profile.

Choosing a Device ¶ 

For this project, we want you to choose a device that you’re excited about working on. It doesn’t have to be a smartphone or laptop! It can be anything from a bike, to a toy, or even a common household appliance. It can even be broken. (You’ll be writing guides to show someone with a broken device how to replace faulty parts, so it’s fine if your device is broken.)

The important thing is to find a device that is NOT already well-documented on iFixit. (A simple search should tell you whether there are already guides for your device on the site.) Your device should also be complex enough that you can write the required number of guides. Each guide will cover replacing one component.

If you have any questions about choosing a device, feel free to shoot us an email.

Project Proposal ¶ 

Once you’ve chosen a device, the next step is to send us a proposal. The proposal should describe what you’ll be working on for the four milestones of this project. The proposal doesn’t need to be long, but we’ll use it to help start your project off in the right direction.

A proposal is required for the project—even if you’re working on an editing project. Proposals allow us to give you the necessary privileges to work on the site without problems. Talk to your instructor for details specific to your class.

Important things to include in your proposal:

  • What device will you be working on?
  • How much repair information is already on the internet about your device? Are there disassembly instructions available? If so, how good are they and how are yours going to be better?
  • What is your proposed device page URL? It should be of the format: www.ifixit.com/device/Device_Name
    • Simply replace Device_Name with the make and model of your device. The device name should include only the manufacturer and model name or number—write it exactly as it appears on the manufacturer's website or in the device's official documentation. Do not include generic terms like "cell phone" in your device name.
    • For example, the device page URL for Samsung's Galaxy S5 is www.ifixit.com/Device/Samsung_Galaxy_S5.
  • What is your proposed troubleshooting page URL? It should be of the format:
    www.ifixit.com/wiki/Device_Name_Troubleshooting
    • The troubleshooting page URL for the Galaxy S5 is www.ifixit.com/Wiki/Samsung_Galaxy_S5_Troubleshooting.
  • What specific problems will you address on your troubleshooting page? Choose at least 5 of the most common problems that users notice with their device. Examples might include things like the device not turning on, not responding to button inputs, performing slowly, etc.
  • What specific guides will you write for your device? Each guide should show how to replace a specific component of your device (battery, display, motherboard, etc.). (You are not responsible for creating a "teardown" or general disassembly guide.) If you’re not sure, check out our Student FAQ for some ideas. Later, you may run into new parts to write guides for, or discover that a guide you had planned to do isn't possible, and that’s okay—your proposal is just meant to be a starting point.
  • Which camera will you be using? Any digital camera of 6 megapixels or greater that can mount to a tripod is acceptable. (Note: this rules out most smartphones.)

Please include a header at the top of your proposal in this format:

  • Device: Epson Canoscan 8800F
  • Team tag: CPSU-DOE-F09S1G1
  • Camera: Nancy's 10MP PowerShot A480
  • Group email addresses: abc@university.edu, etc. (These must be the same email addresses that you and your team members used to create your iFixit accounts.)

Don't forget: include your team tag in the subject line of your email, and CC your team mates!

Focus On: Electronics Manufacturing ¶ 

Device production is messy. Did you know that an average CRT display contains five pounds of lead? Or that creating a single microprocessor requires 70 pounds of water? Electronics manufacturing exerts huge strain on our planet and exposes people in developing countries to toxic chemicals.

Resources ¶ 

View Statistics:

Past 24 Hours: 0

Past 7 Days: 0

Past 30 Days: 0

All Time: 17,234