Following the discussion about my guide
its clear no-one is going to agree on a "standard" strategy.
heres my two pennorth:
1: Generally fritzing is not useful
2: our contributors have vastly different experience and mostly dont know how to lay out an ANSI / IEC compliant schematic, nor what the symbols represent.
Offhand - do you know the symbol for a TRIAC or UJT?
I keep seeing "pencil and paper is fine"; and it is but they need to know how to draw it.
3: before we start arguing about applications we need to cover the basics. A schematic (at a beginner level) doesnt NEED to be standards compliant, but it DOES need to have the info we need - eg parts labelled.
yes, there is a need for concrete examples of schematics for simple circuits.
The button "schematic" is not standards compliant.
There is also the issue of whether our schematics SHOULD be standards compliant. As in the button picture, which is a compromise in that it shows the physical pin layout.
Finally of course there are the "higher level" apps like KiCAD, EasyEDA, EAGLE etc that will do all the work up to generating a PCB.
I'd suggest they should be a totally seperate subject as they are completely beyond any beginner, and mostly unnecessary if you are documenting a circuit on a breadboard.
The simpler apps generally are a useful introduction to these more advanced and powerful apps.
I think Circuit diagram is a good introduction to drawing schematics.