Markdown in /src
perrygeo
13 points
1 comment
September 21, 2026
Related Discussions
Found 5 related stories in 89.0ms across 7,302 title embeddings via pgvector HNSW
- Show HN: Learning Rust by writing a Markdown to HTML compiler deotman · 13 pts · July 29, 2026 · 59% similar
- Show HN: Markdown Viewer and Editor beerglass · 22 pts · August 31, 2026 · 58% similar
- Emacs 31: An unofficial guide to Markdown-ts-mode RahulMJ · 170 pts · August 27, 2026 · 58% similar
- Markdown Database Pattern rufuspollock · 42 pts · August 27, 2026 · 56% similar
- Show HN: Writemark, a dependency free web component for inline Markdown editing _boffin_ · 37 pts · July 25, 2026 · 56% similar
Discussion Highlights (1 comments)
ktpsns
I generally put markdown in /docs. I don't uppercase filenames. Instead I make a documentation generator consume the files so I get a decent navigation in HTML/PDF builds. We did put non-code into /src for a very long time: It was heredocs, multiline docs, etc. Actually my preference is to put texts close to code and only fallback to /docs/something.md at a conceptual level. Which is probably what the author proposes, given that he sees markdown as primary interface to code.