The resources section of a context provider manifest identifies the provider component and its context hook. The editor and runtime use this information to load the provider and route its exposed values and functions to connected components.
The following resources section points to a provider in a Studio Two site project:
A resources section supports the following fields:
| Field | Required | Description |
|---|---|---|
client | Yes | Provider component bundle that runs on the live site. |
contextSpecifier | Yes | Name and module identifier of the provider's context hook. |
editor | No | Separate provider component bundle for design-time behavior. |
The client field identifies the provider component that runs on the live site.
| Field | Required | Description |
|---|---|---|
url | Yes | URL or project-relative path to a module whose default export is the provider component. |
The Wix Extension Builder uses a project-relative path for a Studio Two Data Source:
The contextSpecifier field identifies the hook that the provider component exports.
| Field | Required | Description |
|---|---|---|
hook | Yes | Name of the exported hook. Maximum 100 characters. |
moduleSpecifier | No | Module identifier for the context. Maximum 100 characters. |
Set hook to the exact export name. React hook names start with use, such as useTeamContext.
Connected components receive context values and functions through editor binding as props. They don't call this hook. The provider must still export the hook because the context provider manifest requires it.
For a provider published as an npm package, moduleSpecifier identifies the package that exports the context hook. A project-local Studio Two Data Source can omit this field when the Wix Extension Builder doesn't generate one.
The optional editor field identifies a provider component that the editor loads at design time instead of the client resource. It can provide placeholder values when the live data isn't available in the editor.
| Field | Required | Description |
|---|---|---|
url | Yes | URL or project-relative path to a module whose default export is the design-time provider component. |
Last updated: 2 November 2026