/
/

Site Navigation

Your Account

Choose Language

Options

Creating "sets" of repair guides to match the range of products we use

Is it possible to create a mini "catalog" or "set" of repair guides for later reference?

Specifically, I work with different school districts across California, and each district has their own set of purchased hardware. So one school is using a particular brand of PC laptops, the other a particular Chromebook, etc. Sometimes the districts have the same products (e.g. 3 of my districts all use the same LCD projector), but often times it's a completely unique bundle at each district.

Rather than steering them to individual pages, I thought it might be really cool idea if ifixit developed the ability to create "site sets", with the ability to use headers and organize repair guides in a logical order. Nice to add the district's logo too!

So you could imagine a "School District A fixit guide" that was a collection of all of the relevant repair guides. That would be so insanely cool!

Thanks for considering this request!

-Chris

SchoolTechnologyLeadership.com

Answered! View the answer I have this problem too

Is this a good question?

Yes No
Score 1
2 Comments

Is this for content you'd like to create, or for guides/wikis that already exist on the site?

by

Hi Evan. Well, I guess it could be for both. But my original thinking was to make collections of existing ifixit guides. Wouldn't it be cool to log into a "school page" or "district page" and find a list of all of the equipment that was in use at the school, with the fixit guides right there, organized by type? If guides were missing, you could also list that and put out an "all-call" to the school community for help in creating the additional missing documentation. That way you would have a single page resource that linked to all of the school's equipment. Same thing could apply to a company or other organization, I suppose, but my interest is in supporting school tech deployments. Even cooler would be a way to indicate how many items at each school were in need of repair or parts, and a way for community members to "purchase" the spare parts or replacement parts needed for maintenance of the equipment. I think iFixit is uniquely positioned to do this (though I want all the credit - just kidding).

by

Add a comment

1 Answer

Filter by:
Most Helpful Newest Oldest
Chosen Solution

Options

Alright, I think you can accomplish what you're trying to do using Teams. Here's an example of a Team Page on iFixit. If you poke around a little, you'll see that every team has members, a collection of team member contributions (guides and wikis made by team members), and an optional wiki page.

That wiki page can include all sorts of information, but I think you can benefit from the Dynamic Lists feature that all of our wikis support.

I created an example wiki as an example of how you I would arrange this information, but obviously feel free to organize it however it makes sense:

Block Image

Here's the markup text I used to make that page:

== About ==
This is the repair wiki for laptops and tablets used in district.

== Laptops ==
'''Samsung Chromebook Series 3'''
[guidelist|device=Samsung Chromebook Series 3]
'''Acer Chromebook C710'''
[guidelist|device=Acer Chromebook C710]
'''[[Acer Chromebook C710 Troubleshooting|Troubleshooting guide]]'''

If this sounds like a solution that works for you, head over to our Team Creation Page and get started. If you have any more questions feel free to get in touch!

Was this answer helpful?

Yes No
Score 1

4 Comments:

This is exactly what we needed! Thanks Evan. I'll go try it out!

by

So you mostly got it right, buuut...

You made a new wiki page (https://www.ifixit.com/Wiki/SchoolTechno...) on iFixit for your set of repair manuals, and ideally we'd like to contain all the content for your business within your Team's wiki pages (https://www.ifixit.com/Team/About/22168/...).

This is because the content of that wiki is targeted at a specific group of clients rather than the public at large (and allowing businesses to make targeted content is a slippery slope).

I realize this was likely oversight on your part, so I'll let you migrate your content from the wiki page to your team's page—if you can't figure it out, let me know and I'll post a quick how-to.

If this content model is too restrictive, consider starting your own Dozuki nanosite. This will let you have a single repository you can point your customers to, and will be entirely owned and controlled by you without interfering with iFixit's content policy.

by

Thanks Evan. Yeah, I need a very explicit step-by-step. I got stuck on how to add the content (e.g. this looks like a mark-up language that is unique to ifixit, and I'm not familiar with it.

Maybe we can create a document that walks someone like me (IT Director types) through the process of creating the Team wiki page, identifying the markup language that is associated with each product, and then assembling the content onto the page.

I really appreciate your help in this. I think it will be very helpful in the future to have these school or district team pages. It might also create some cool cross-district collaboration when it becomes clear who is also using the same equipment (and thus may have the same repair issues/questions/challenges/solutions).

by

Also, just FYI. I'm not a business. I work directly for an individual school. Just wanted to make that clear. :)

by

Add a comment

Add your answer

Chris Moggia will be eternally grateful.