Open LinusSkucas opened 6 years ago
Thanks so much for the suggestion @LinusS1. At the moment because our documentation is changing so rapidly - ie multiple changes per week - I'm not sure that it makes sense to have a PDF version, but if there is significant demand for this I'm happy to investigate.
Alright! Thanks!
Hey, I had another quick look at this as there's an option with the new platform we use - Gitbook.
Unfortunately it would cost us a few hundred per month as it's in a premium tier that we don't have the need for. Looking at the features I can't see us upgrading to that until our "technical writing team" has 10+ staff (...keep dreaming gez)
So it would make more sense to use something like a Github Action / Jenkins pipeline to build it. This won't be a priority for us internally, just outlining the most likely way forward in case anyone wants to give it a go.
It would be nice to have the documentation available as a pdf file. This would make it possible for off line viewing and allow people to put it on e-readers such as kindles.