Both documentation and guidelines are livinig documents open for contribution. Please ask any questions, dillemas, suggestions as github issues on this repository so others can benefit from recorded answers and discussion.
Be sure to check both definition guidelines and documentation guidelines before you start writing specifications and documentation.
For general software documentation writing style and terminology, see the Microsoft Manual of Style.
Following tools can help you write swagger and markdown text files:
- Api Studio
web based
yaml+swagger
json+swagger
- Stack Edit
web based
markdown
- Visual Studio Code
desktop
markdown
yaml
These are just suggestions, you are wellcome to use different tools or work in notepad if you prefer
Use Autorest to generate client library in C# and verify that generated code compiles properly.
See how we organize documentation source files.
This is how we produce documentation site from source files:
- Documentation writer checks-in yaml / markdown file
- Build script converts swagger files from yaml to json
- Build script generates static html from markdown using templates and pretzel tool
- Build script publishes documentation site