Runnable examples
Try every extension point as a complete plugin
Every example is a project with a manifest, a build target and activation/deactivation code. Build it and select its folder in Developer Mode instead of relying on isolated snippets.
| Example | Covers | Location / check |
|---|---|---|
| Character-count panel | CSS, SidePanel, ActiveNoteEvent, settings, commands, toolbar, keys | Template root. Switch notes and change settings |
| Table of Contents | Markdown heading parsing, note events, line navigation | ToC. Test fenced code, Setext and duplicate headings, then click to scroll |
| Blue Theme | Theme palettes and conditional extra CSS | official theme plugins. Select it in Appearance and switch light/dark modes |
| Markdown / editor | remark, rehype, CodeMirror | examples/markdown-editor. Check the added preview/export message and line wrapping |
| Notes | Root listing and note creation permissions | examples/notes. Its panel button creates a note only when pressed |
| Network | Declared destinations and HTTP responses | examples/network. Its panel button fetches GitHub Zen and displays the response |
| Clipboard / links | Clipboard and external URL APIs | examples/clipboard-links. Run actions from panel buttons |
For each template example, run pnpm install, pnpm typecheck, pnpm build, pnpm test in its own directory, then select that directory in Developer Mode. Notes requires a registered root folder. Network and clipboard actions require their corresponding consent. The delete API always asks the user for confirmation.
Customize an example
Rebuild after changing a manifest ID; the virtual API path follows that ID. Do not replace API/shared-module imports with local runtime copies.
Activation only registers extensions and returns within ten seconds. Cleanup also removes the panel's own DOM. Note, network and clipboard operations are invoked by commands corresponding to user-pressed buttons.