From today's call, we have "low level" resources on the learn website (how to do Foo with standard Y). And that's a great way to get started.
Now, if people want to elevate their learning with patterns and practices, and guidance to apply on how to well structure their documents, it seems we have a gap today.
A good candidate for that would be something like adding a specific metadata to all operations (like a sunset header) or a status code to all operations (like a specific throttling response). (using overlays)
A better example can be found here. OAI/OpenAPI-Specification#5193 (reply in thread)
From today's call, we have "low level" resources on the learn website (how to do Foo with standard Y). And that's a great way to get started.
Now, if people want to elevate their learning with patterns and practices, and guidance to apply on how to well structure their documents, it seems we have a gap today.
A good candidate for that would be something like adding a specific metadata to all operations (like a sunset header) or a status code to all operations (like a specific throttling response). (using overlays)
A better example can be found here. OAI/OpenAPI-Specification#5193 (reply in thread)