280 markdown files, 123 React components. I counted my repo the wrong way round.
by•
I counted the tracked files in my main repo this morning, expecting the code to dominate.
280 markdown files. 123 React components. The markdown runs 427,099 words. The components run 23,394 lines.
186 of those 280 markdown files were first committed in August 2026, inside one month. 111 of them sit under a single docs/seo folder.
Every one of them felt like work while I was writing it. An audit of a problem reads exactly like the fix for it, right up until you go looking for the commit that changed the code.
The rule I am putting on myself is that nothing new goes under docs until the thing it describes exists in the app.
If you have ever counted, what came out on your side?
34 views
Replies
280 markdown files sounds crazy until you realize how much of the product depends on them.
i'd probably keep the markdown too but tie it more closely to what actually live. that makes the doc much easier to trust.
The markdown isn't bloat, it's the product. I'd worry more the day the code outnumbers the pages.
counted ours. 299 markdown files against 279 react components, so nearly the same ratio as yours. 691k words of markdown against 204k lines of ts.
the part that bothered me is where they sit. 147 of the 299 are in one folder, 75 plans and 72 specs, so the biggest thing in there is documentation of work rather than of the product. 151 of them landed in a single month.
one thing that flatters my number though. 81 files are the same 27 documents in slovenian, spanish and german, so a chunk of the pile is translation and not writing.
your rule is stricter than ours. we only delete a spec when the thing ships, and mostly we dont.