3 ms·
I don't call it "art", but I've been putting textual diagrams into documentation lately, and I think it can be very helpful. For example, I added a diagram to
by nathan_long 9y ago
I don't call it "art", but I've been putting textual diagrams into documentation lately, and I think it can be very helpful.
For example, I added a diagram to the Phoenix Channels guide, showing how the implementation works: https://github.com/phoenixframework/phoenix/blob/master/guides/docs/channels.md#overview https://github.com/phoenixframework/phoenix/blob/master/guid...
I use Monodraw (https://monodraw.helftone.com/ https://monodraw.helftone.com/), which lets you work with boxes, arrows, etc as objects in layers, and export to ASCII or Unicode. ASCIIFlow (http://asciiflow.com/ http://asciiflow.com/) is a simpler alternative.
- Gracana 9y agoYour ascii diagram wraps terribly on an 80 column screen, which is the typical width for a text display.
- craigds 9y agoIf you live in the 80s.
- sowbug 9y agoDepends on whether you consider the extra columns to be yours or those of your audience. If they're yours, use them however you want. If they're your audience's, then stick to the 80-column standard so your readers can tile standard-sized windows the way they want on their large monitors. Especially important for side-by-side code diffs.
- kevin_b_er 9y agoYour art looks great on linux, but looks terrible on Chrome on Windows. All the line art is misaligned.