I’m trying to figure out the most useful format for sharing build procedures in this category before we get a lot of content posted in different formats. Because the format matters: a wall of text with no structure is hard to follow mid-build when your hands are covered in finish or solder flux.
Here’s what I’ve been thinking about based on what I’ve wanted when reading other builders’ documentation.
Materials list first, with specifics. Not “sandpaper” but “180, 220, 320, 400, 600 grit sheets, plus a sanding block for flat sections.” Not “wiring” but “22AWG hookup wire, cloth-covered preferred for heat resistance near the iron.” When I’m sourcing supplies before a build, vague materials lists are nearly useless.
Step-by-step process with decision points called out explicitly. The most useful build documentation I’ve read doesn’t just say what to do, it says what to check before moving to the next step. “Sand to 220, then wipe with naphtha and look for scratches under raking light before proceeding to primer.” That’s more useful than “sand then prime.”
Time estimates. How long did a step actually take you, and how long should someone budget? Finishing stages especially benefit from this because dry times between coats vary by product and environment and skipping them has real consequences.
Photos at key stages. Not glamour shots of the finished guitar. In-progress photos of: the neck pocket fit before glue-up, the wiring before the cavity cover goes on, the finish at the wet-sand stage. The ugly middle of the process is what’s actually useful.
What I’m less sure about: video versus written. Video is easier to follow for physical techniques but harder to reference quickly mid-build. Written recipes are easier to scan but harder for showing motion-dependent skills like soldering or fret crowning.
When you’re reading someone else’s build documentation, what’s the most useful element and what do you find yourself wishing was included?
Would you rather read a detailed written recipe with photos, watch a video walkthrough, or have both?
If you were writing up your own build recipe, what would be the hardest part of your process to document clearly?