Drop a markdown document with Go code into the editor and it comes back rendered, the Go blocks highlighted; Share then hands you a read-only URL for the finished page.
Go teams lean on short written documents. A design note argues for a worker pool instead of one goroutine per request. A postmortem quotes the handler that leaked connections and the patch that fixed it. A platform team documents the pattern every service should follow for context cancellation. These notes travel through chat and tickets, and they lose their shape on the way: indentation inside a select statement collapses, and the code becomes difficult to follow.
Here, the text keeps its headings and lists, and Go keywords like func, defer, go and chan, along with strings and comments, are colored. That makes it easier to trace where a channel is closed or which branch returns an error. You can also put a Mermaid diagram next to the code if the note needs a sequence of calls; it renders in the same preview.
Nothing here runs go vet or the compiler; the page shows the code as written. Recipients do not need an account. The link is not listed in search results, and the document expires on its own after 15 days, which matches the lifetime of most incident threads. If the note should outlive that, export it as .md and keep it with the repository.
How to view Go in markdown
- Paste your markdown into the editor above, or edit the example.
- Wrap Go code in a fenced block that starts with ```go.
- The preview shows the rendered document with the code highlighted (side by side on desktop; switch to Preview on a phone).
- Select Share to get a read-only link that anyone can open without an account.
Frequently asked questions
Should I tag blocks as go or golang?
Use ```go. That is the tag the highlighter registers; ```golang is not mapped, so a block with it shows as uncolored monospaced code.
Does the viewer run gofmt on my code?
No. Code is shown exactly as you pasted it, including tabs. Nothing is formatted, compiled or checked.