The SDK repository includes React, Vue, Angular, and native adapter surfaces, but their official customer-support level and documentation depth remain backlogged.
Choose an integration approach
- Use the core JavaScript SDK when framework-neutral ESM integration is sufficient.
- Evaluate the repository’s React, Vue, Angular, or native entry point only when it matches the application architecture.
- Confirm the adapter’s current documentation, exported surface, release state, and support commitment before using it for a customer implementation.
Implementation checklist
- Confirm the target runtime and framework version.
- Verify that the required authentication, CRM, file, or navigation capability exists in the selected entry point.
- Build a minimal safe test using the connected WoodsPortal API.
- Confirm state, error, and session behavior.
- Record the exact adapter version and support decision in the implementation documentation.
Current qualification
- Repository entry points prove that adapter surfaces exist, not that every adapter has the same public support commitment.
- Do not publish a universal supported-framework matrix until the backlog item is resolved.
- The dedicated developer portal remains an in-development surface and is not a production customer-facing application.
[Visual placeholder: SDK adapter map and minimal examples | Verified adapter versions | Run one supported example per approved adapter | The documentation distinguishes implemented entry points from officially supported customer adapters.]