Plan and create APIs specifications with OpenAPI/Swagger

The obvious pronunciation foibles aside, this is exactly what I was looking for: a fast paced, hands-on, example of a workflow, and the steps to create the specifications from business requirements. So far, so good. My only criticism, incorporate the use of git hub Projects board and creating templates vscode directly. You can do all the same in a template markdown file, have it open parallel to the YAML file you're writing, and then run the preview. The addition of Trello, while a good tool, added a layer outside of my usual workflow. UPDATED: Also, while you incorporate GitHub at some point, It may be worthwhile to slow down and when you fix the errors, or implement a path, create the commit message in VS Code, do the fix, then commit. This way, you kill two birds with one stone: - Making small changes to code and committing them: in your changes and implementations (my errors weren't the same, as I tried to type much of it out to aid memorizing the process), you burn through the steps fast. IRL you'd probably want to keep a record when you change things. - You double up and make a git tutorial as bonus material, showing newbies, myself included for many things, some best-practices in action. Just an idea. Version 2.0 perhaps? Anyway, thanks for this!