I am writing in PHP, and I am trying to write docs for an existing API, but also figure out the best way to write docs for future projects
On Wednesday, April 26, 2017 at 4:39:06 PM UTC-6, Ron wrote: > > 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] <javascript:>> on behalf of Nick > D <[email protected] <javascript:>> > *Reply-To: *"[email protected] <javascript:>" < > [email protected] <javascript:>> > *Date: *Wednesday, 26 April 2017 at 14:58 > *To: *Swagger <[email protected] <javascript:>> > *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] <javascript:>. > 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.
