Hi Nick,
There are several approaches you can take, but they depend on whether you’re trying to document an existing API or write up a new one. Which is it for you? If an existing API, which language/framework do you use? From: <[email protected]> on behalf of Nick D <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, 26 April 2017 at 14:58 To: Swagger <[email protected]> Subject: Best Practices for writing Swagger Docs Hello, I am wondering if there is a place that would let me know if there are any good practices with using Swagger to document my project? If there isn't, what are some opinions on how to best write and maintain Swagger documentation? -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
