Shuffle ball change: Sashay your way to clearer API documentation
summary
Claims a practical path: she cleans scattered microservice references with a spreadsheet to model every endpoint, authors an OpenAPI spec in OpenAPI YAML with Redoc Pro and moves tooling from Go Swagger to swagger yard, balances owning a spec while keeping up with five developers, edits commits directly in feature branches, and introduces a style guideline that increases consistency. Automation adds reviewers via a GitHub action adds docs team as reviewers. Outcome: clearer, more consistent API reference readying internal and external use.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:03Secret Benefits
- 3:02How We Provide Value to an Organization
- 8:22Preparation
- 11:39Authoring and Maintaining the Api Spec
- 16:31Api Documentation Guidelines for Back-End
- 20:56Feedback
- 26:54Impact the Process
- 28:13How Much Programming Ability Did You Have under Your Belt before Getting into Api Docs
- 29:18Suggestions on Beginner Languages
- 30:16How You Got Yourself To Be Automatically Listed as a Reviewer in Github
- 31:44Was the Tech Writer Involved in the Sprint Review
- 32:33How Do You Find Projects That Need some Api Doc Help
related talks
35mDocumenting APIs: new era, same craft
21mLet there be docs!
38mZen And The Art Of Automanually Creating API Documentation - An Inquiry Into Process
01h 01mOpenAPI & .NET: You're Doing It Wrong
35mOpenAPI for Documentarians
24mBuilding an Accessible API Spec with Traditional Engineering Teams
27mGetting developers hooked on your API
46mOpenAPI & .NET: You're Doing It Wrong!
