01
A README is read before the code
A route table or a directory tree at the top of a README answers the first question a stranger has. Lines stay put in a monospace block, and a diff of the README shows only the row that changed.
Pikkola Diagram Studio, tool No. 49
A table, a directory tree, a callout box, a flow line and a block banner, drawn in plain characters. Paste the data, pick the style, and copy text that keeps its columns in a README, a code comment, a commit message or a terminal. Nothing leaves this tab.
The studios
Each studio writes a block of text. Copy it and paste it where the diagram belongs; nothing is rendered, so a README shows the same picture as the terminal.
Comma, tab, semicolon or pipe is detected from the first line. A quoted cell may hold the separator, a line break or a doubled quote.
Click a cell to type in it. Enter moves down, Tab moves across, and the button above each column cycles left, centre and right.
One level per indent step: a tab, or two or four spaces, whichever the first indented line uses. A word after # becomes a comment on the right.
Split on an arrow, a comma, a pipe or one step per line. Long steps wrap inside their box.
Twenty four letters at most, set in uppercase from a built-in 5 by 7 font. A character with no glyph is named under the banner.
The characters
The same three cells in every style. Pick by where the block is going: a terminal, a plain text file, or a Markdown renderer.
| Style | Where it survives | Out |
|---|---|---|
| Unicode box | A modern terminal, a code editor, GitHub | ┌───────┬─────┐ │ route │ 200 │ └───────┴─────┘ |
| Heavy box | A heading that should carry weight | ┏━━━━━━━┳━━━━━┓ ┃ route ┃ 200 ┃ ┗━━━━━━━┻━━━━━┛ |
| Rounded | A note or a callout, softer than a box | ╭───────┬─────╮ │ route │ 200 │ ╰───────┴─────╯ |
| Double | A summary table, a little formal | ╔═══════╦═════╗ ║ route ║ 200 ║ ╚═══════╩═════╝ |
| Classic ASCII | Anything, including a font with no box characters | +-------+-----+ | route | 200 | +-------+-----+ |
| Markdown | A renderer that will draw the table itself | | route | 200 | | :---- | --: | |
Where it goes
01
A route table or a directory tree at the top of a README answers the first question a stranger has. Lines stay put in a monospace block, and a diff of the README shows only the row that changed.
02
A pipeline drawn above the function that runs it saves a reader from assembling it in their head. Put it inside the file's own comment style, so it looks like the code around it.
03
Two boxes and an arrow say what moved and what stayed. Nothing is rendered in a commit message, so the characters are the diagram, and a plain ASCII border is the one that survives every tool in the chain.
No. Every diagram is drawn in this tab. The draft is kept in this browser's local storage so a reload does not lose it, and the page's own content policy sets connect-src to none, so a request could not leave even if one were attempted.
In a monospace font, yes. Every cell is padded by display width instead of character count, so a Korean or Japanese word, which takes two cells, keeps its column. In a proportional font, in email or in a chat window, no table lines up no matter how it was made.
A Unicode box is the most readable in a terminal and in a Markdown file. Classic ASCII with plus and minus signs survives a font or a parser with no box-drawing characters. Markdown is the only one a renderer turns into a real table.
Because a Markdown table needs one: the row of dashes is what tells the renderer it is a table, and the colons in that row carry the alignment you chose for each column. With the header row switched off, the separator is left out and the pipes are just text.
The first indented line sets the step, so two spaces, four spaces and one tab all work. A line deeper than the one above becomes a child, a shallower one closes levels, and the tree is drawn with the usual branches. Comments after a hash can be lined up on the right.
The font holds A to Z, 0 to 9 and the common punctuation. Letters are set in uppercase, and a character with no glyph is named under the banner instead of being drawn as a question mark or a box.
Yes. The studios stack, the output scrolls inside its own card rather than the page, and Copy writes to the phone's clipboard.