Re: What's the most favourable way to get documentation as an automated process?
nim jsondoc -o:doc.json I use this for [https://github.com/treeform/mddoc](https://github.com/treeform/mddoc)
Re: What's the most favourable way to get documentation as an automated process?
@shashlick Did you have something in works that generated JSON Nim docs?
Re: What's the most favourable way to get documentation as an automated process?
The documentation builder also builds `.idx` files that might be easier to parse, but you need to do some tinkering to figure out where `koch docs` outputs these.
What's the most favourable way to get documentation as an automated process?
I am writing a small tool for my personal use. It's main task is to get a keyword from the command line and fetch me the relevant documentation proc/template/macro/const from the nim standard library without me having to open the web browser and searching for it myself. What's the best way to fetch documentation in your opinion? At this point I'm thinking of parsing the stdlib index([https://nim-lang.org/docs/theindex.html](https://nim-lang.org/docs/theindex.html)) but I was wondering if there is any more robust way to do so.
