At EkLine, our customers each had their own documentation frameworks. One used Fern for their API documentation. Their requirements went beyond what the Fern docs covered out of the box.So I dug in. Experimentation over reference material. Working around gaps, finding undocumented patterns, figuring out what was possible through hands-on use. In the process, I learned Fern well enough to see where the documentation itself could be better.
PR #397: Reference documentation for API endpoint filtering
Practical improvements born from actual usage: the kind of thing you only notice when you're solving a real problem for a real customer.
Why This Matters
The best open source contributions come from people solving real problems. I wasn't building an open source profile. I was helping a customer. The contributions were a side effect of doing the work properly.The gap between "how a tool works" and "how the documentation explains it" is where the most useful work happens. Finding that gap requires using the tool in anger, not just reading about it.
