On this page
Start a conversation
For editorial questions, correction reports, and collaboration proposals, email [email protected]. The link opens your device’s email application; there is no contact form or account registration on this site.
Give your message a useful subject, such as “Article correction: OpenAPI validation” or “Topic suggestion: delegated tool authorization.” Include the page path when the message relates to an existing guide. A concise explanation and a primary reference are more useful than a large unstructured attachment.
Suggest a correction
Identify the passage, explain the concern, and provide the version or configuration that changes the conclusion. Separate a factual error from an implementation preference when possible. The editorial policy explains how sources and examples are treated.
Security details often depend on the application’s trust model. Describe the boundary involved without sending production credentials, private documents, customer data, or secrets. Use sanitized examples that preserve the behavior you want to discuss.
Share a topic or collaboration idea
Tell us which audience the idea serves and which question the material should answer. Good topics connect a concrete workflow to decisions developers can test: a permission matrix, a request contract, a tool approval, or a recovery path.
Do not submit claims of affiliation, endorsement, or measured performance without evidence. The reference library shows the kind of primary material used to ground the site’s technical explanations.
Report a problem with this website
Include the page path, device or browser, steps to reproduce, and the visible result. For an accessibility issue, describe the assistive technology or interaction involved when relevant. The accessibility page describes the site’s navigation and motion controls.
Keep any security report focused on a minimal, non-destructive reproduction. Do not access another person’s information or test systems you do not own or have permission to assess.