As some of you might have noticed in the freshly baked September Iteration Plan, one of our focus this month is extensibility documentation. Which comprise of:

• The "Extension Authoring" and "Extensibility Reference" sections on our doc page: https://code.visualstudio.com/docs
• https://github.com/Microsoft/vscode-extension-samples

Some of the issues we are already aware of:

• API Reference is hard to use: https://code.visualstudio.com/docs/extensionAPI/vscode-api.
• Some topics (for example, Proposed API) have information scattered throughout release notes, wiki and GitHub issues.
• The API sections on the website could improve its organization to have better topic categories & depth progression.

We'll try to address those issues. But we also want to hear from you, the extension authors.

While you are trying to write VS Code extensions, which doc page is hard to understand? What are the issues you run into? On what topic were you unable to find useful information? How can we make the process more enjoyable for you?