Learning Path
If you are new to the SDK, use this order.Step 1: Understand The Runtime Split
Read:README.mddocs/RENDER_RUNTIME_CONTRACT.md
- understand backend runtime vs iframe runtime
Step 2: Learn Safe Plugin Authoring
Read:docs/SAFE_PLUGIN_AUTHORING.mddocs/EXTENSION_POINTS.md
- learn what is public contract vs anti-pattern
Step 3: Start From Fixtures
Start from:examples/fixtures/minimal-plugin.fixture.tsexamples/fixtures/error-handling-plugin.fixture.tsexamples/fixtures/storage-plugin.fixture.ts
- get a production-friendly starting point instead of copying learning examples blindly
Step 4: Learn Capability And Privileged Actions
Read:docs/HOST_PRIVILEGED_ACTIONS_CONTRACT.mddocs/API_STABILITY.md
- understand what the host owns
- understand what capabilities are required
Step 5: Use Numbered Examples Intentionally
Use numbered examples only after the fixtures make sense. They are a teaching progression, not the default production starting point. Good examples to visit next:examples/05-advanced-dom-plugin.tsexamples/08-privileged-actions-plugin.tsexamples/09-operator-plugin.tsexamples/13-service-content-hub-plugin.ts
Step 6: For Provider Integrations
Use the connector pattern:- host owns transport and session state
- plugin owns provider-specific parsing and UX
docs/SHAREPOINT_PROVIDER_HOST_CONTRACT.md
Practical Outcome
If you follow this order, you avoid the common mistakes:- mixing runtimes
- misusing
render() - skipping
renderHTML(...) - using stores too early
- treating examples as stronger than the actual public contract