Our documentation currently pulls in code snippets directly into Markdown files through a custom annotation syntax from 67 external repositories. If we switched to Bluehawk (so that all code snippets would be browsable in our documentation in one folder), would our compilation script first have to download every single code repository locally, or can Bluehawk generate snippets from a file in Github at a URL?
If remote file reading is not possible, are there any significant challenges for us making a pull request to Bluehawk to add the feature? Would the architecture require an overhaul?
Thanks.
Our documentation currently pulls in code snippets directly into Markdown files through a custom annotation syntax from 67 external repositories. If we switched to Bluehawk (so that all code snippets would be browsable in our documentation in one folder), would our compilation script first have to download every single code repository locally, or can Bluehawk generate snippets from a file in Github at a URL?
If remote file reading is not possible, are there any significant challenges for us making a pull request to Bluehawk to add the feature? Would the architecture require an overhaul?
Thanks.