Talk:Repair Wiki

Discussion
If you are authorized to make decisions by Louis or a Rossmann Group employee, feel free to mark "[yes]" after any point to signal that the suggestion should be followed through.

List of details that may need to be added in the future

 * change the front page to about the organization and create separate pages for standard etc.
 * requirements for membership
 * how to apply
 * how standards will be enforced
 * differentiate standards (required regulations) from best practices (highly encouraged but not mandatory)
 * how to suggest/appeal standards {suggesting or appealing standards should be done via this system, but should require approval from a moderator - rather than allowing anyone to edit and it immediately updating the public page.}

Possible changes to standards/formatting/categorization

 * move 16 and 17 to customer interactions
 * move answering phones under customer service
 * move 30 and 31 to customer communications
 * move 32, 33, and 34 to handling of customer devices
 * move 35 to customer communications
 * move conduct under internal operations
 * "When talking to someone on the phone, if they want an estimate over the phone, tell them that it’s a general estimate that may not apply to their device and that we would need to take a look at the device itself.." and "When talking to someone on the phone, if they want an estimate over the phone, tell them that it’s a general estimate, and it may not apply to their device, we would need to take a look at the device itself.": something is repeated, one should be removed.
 * "Emailing customer service" category is mostly the employee rules that are more than manners and talking to customers, and should be renamed
 * I would suggest to move 23 to "Specific to Louis" :)

Possible new standard

 * transparency as far as parts origin goes. Never say "new part" making the impression this means "new factory genuine part from OEM" when it doesn't. The client should be given clear options: use a cheap aftermarket/used part, a good quality aftermarket part, be referred to the OEM. The client should be informed of risks of using aftermarket parts (Error 53 case), especially in the context of ongoing part serialisation.(Lacek)
 * something about "warranty"? Perhaps this should not be standarized. In any case there are genuine cases where warranty cannot be honestly given ("partial repair" explicitly requested by the client)
 * worker safety as far as: resin flux, solvents, cleaners, IPA go (gloves / *proper* mask / quality fume extractor ).

Clarification required
It should be more clear what is the scope of these standards. In the current for they clearly apply to Louis-like business (Macbooks/other brands/phones) but should they apply to e.g. e-bike service center or electric car battery repair service? If yes, then some of these standards make little sense (like 21, when "the whole machine" may be 2 tonnes) or other standards may be missing (in this case especially related to the battery). There are other, more specific important, standarizable things specific for home appliances, precision lab equipment, high voltage equipment, medical eequipments, or machinery used in food processing.

Websites and Google Business
I think that adding an area about online services may be good. Many repair shops should have a focus on their website and internet traffic as a whole as many potential customers search online before they visit.

Non-Rossmann work items
Hi Louis, I (Kingdud (talk) 21:22, 23 August 2020 (PDT)) am answering your call to help you organize and make changes to this wiki. What do you want tweaked? For starters, I could break the front page into sub-pages. It would look the same, but each section would be its own page (this makes large pages more manageable). Additionally, if you wanted to include, say, the Customer Interaction section, on multiple pages, it would allow you to have one Customer Interaction page that shows up in 4 places, but you'd only need to edit one page and all 4 places would automatically update. The mediawiki feature for this is called 'templates'. It's already built in to the software you are running. This would also allow each page to exist in its own category, with any page using that template automatically inheriting the categories of any templates that appear on that page.

Is there any other way I can help out? Also, e-mail for this wiki doesn't work. I understand if that is intentional. But in case it wasn't, I cannot receive e-mail from this wiki on either gmail nor my personal domain (via mxroute).

Hi all, I Unknown h (talk) agree with Kingdud creating sub pages is must, I would also look at changing the welcome page to something more inviting. In stead of just basic information it could set out the aim of the wiki, goals for it and introduce this organization that Rossmann has talk so much about. You should probably set a too do page as a first priority(I know that the discussion page is currently being used for this but something that is a bit more formal and for the whole website would be good),this would allow other people to contribute to the wiki in an ordered fashion.

Hi. I Psilbern, 2020-08-24 22:52 agree with the multiple sections and the welcome page being a landing page to other content. I also think that all content should be accessible eventually via clicking on links. For example the How to Clean a Motherboard isn't accessible other than search.

Louis if you want a temporary logo please add this line to your LocalSettings.php after the $wgScriptPath line source

$wgLogo = $wgScriptPath. '/images/c/c2/RossmannWikiLogo.png';

I think that the name given to this wiki, “Repair industry best practices and standards”, is too long, even if purely for technical reasons; it cuts off at the end of the search box and also spills over the edge of the header on the Timeless skin. I also agree with the points made by Kingdud, Unknown h, and Psilbern above regarding organization and accessibility of wiki content. Hālian (t / c) 23:57, 27 October 2020 (PDT)

Fae here. I would like to recommend just ditching MediaWiki while you are still starting out!

DokuWiki is easier to manage if you don't have the time or a dedicated web-admin stooge to do it all up for you.

Everything in MediaWiki's software is a manual process. Every feature you need MediaWiki to have is an extension. No part of MediaWiki can check for or apply updates. You'll find very few useful settings panels. Almost nothing for user management or anti-spam/vandalism out of box. Every extension or feature you use needs manually configured in a settings file, and every time you update the core or an extension you'll need to double-check nothing has changed that might break your current configuration and expected experiences. Anything more modern than MediaWiki will no doubt save you time as you continue this project.

Why am I saying this? MediaWiki works great for Wikipedia! Why not you? Put simply, it isn't software made for the masses by the masses. It is made by Wikipedians for Wikipedia and the MediaWiki Foundation. End-users and system admins alike don't have much place in their bureaucracy. Save yourself the time and frustrations by just avoiding MediaWiki from the start. If you need me to expand more on why you should avoid MW - feel free to email me. This message is not sponsored - I have simply grown to hate the software over years of managing it for others.

Software Section Proposal
Morning (Sept 2nd, 2020). I Bernard, (talk) added a page called Software. Added mostly GNU license software for schematic viewers. Hoping this page can be added to the sidebar. This page I'm hoping can guide those who need software to help manage their hobby for board repair or possible buisness venture in the board repair industry. Would like feedback as to whether or not this page is acceptable for this wiki. Thank you.

Translation
Would a translation and localization effort be welcome in this project?