Features Overview

Purpose: provide or link to a document that lists features and which SDK(s) support each feature.

This page is a placeholder that should either include the features document or link to it. Do not add feature data here unless it exists in the source document.

How to add the features document to this page:

• If the document exists as another GitBook page, include it with a content include (recommended for syncing across pages).

• If the document is an external URL or a downloadable file, add a link or embed it.

• If you want a simple reference, add a link to the document with query parameters preserved.

Examples

Include another GitBook page (replace the path with the actual page path):

{% include "/path-to-features-document" %}

Embed an external URL (e.g., a public document or page — replace URL with the actual link):

https://example.com/path-to-features-documentexample.com

Link to an external document (keeps all query parameters intact):

Features and SDK support — external document

If you prefer to keep the content on this page, add the feature list in a clear structure such as a table:

| Feature | Supported SDK(s) |
|---------|------------------|
| <Feature name> | <SDK A>, <SDK B> |

Or use headings per feature with SDK details underneath:

## Feature name

Supported SDK(s):
- SDK A
- SDK B

Next steps

1

Add an include

1. Create or locate the document that lists features and SDK mappings.

2. Place it in the desired GitBook path.

3. Replace the include path above with the real path.

2

Or add an external link/embed

1. Verify the external URL and query parameters.

2. Replace the embed or link example above with the real URL.

FAQ

What if I only have a spreadsheet?

You can export the spreadsheet to Markdown or a public URL and then use one of the methods above (include, embed, or link).

Can I convert a numbered list of steps to a stepper?

Yes — long numbered steps are better represented with the stepper block. Use the stepper examples above.