Studio Two offers a suite of features that support an efficient and productive development workflow. This overview covers the key features that help you develop, test, and maintain custom sites with advanced functionality.
The Code tab is a Visual Studio Code environment built into the Studio Two editor. It includes the Wix Extension Builder for scaffolding extensions, Aria for AI-assisted coding, and a terminal for standard development tasks. For what the tab contains, see About the Code Tab.
Studio Two's component model gives you 3 types of components to build with.
Editor React Components (ERCs) are the recommended way to build custom UI. ERCs are React components you place on pages in the Studio Two editor. They use a manifest-driven approach that enables editor integration, automatic settings panels, and type-safe binding to Data Sources.
Data Sources are logical components that share state and behavior across multiple ERCs on a page. Data Source is the Studio Two UI name for a context provider extension. A Data Source exposes values and functions through a context provider manifest, and ERCs connect to it through editor binding. Wix provides Data Sources for business solutions like Wix Stores and Wix Bookings, and you can add your own for site-specific needs. Wix also creates Data Sources for each CMS collection.
Function libraries are bundles of reusable functions that components can call through editor binding. Useful for formatting, calculations, and other shared utilities.
Site widgets are custom HTML elements you can place on pages. They offer an alternative to ERCs when you need to integrate non-React code or work with existing web components.
Embedded scripts are HTML or JavaScript fragments that load in the site page head or body. Useful for analytics, tracking, and 3rd-party integrations.
Site plugins fill predefined slots on Wix business-solution widgets in the Studio Two editor. As Wix business solutions migrate to the ERC and Data Source model, site plugins become less necessary. You'll work with Wix-provided Data Sources and your own ERCs directly. Site plugins remain available for the current generation of Wix business-solution widgets while that migration is underway.
Develop backend code, hosted by Wix, to build advanced features and integrations.
HTTP endpoints are backend routes that your site's frontend code calls to run logic on Wix servers. Use them to call 3rd-party APIs with secrets, make elevated Wix API calls, and validate data before you save it.
Backend events are custom server-side logic that runs when a Wix platform event fires, such as a new contact being created or an order being placed.
Service plugins are custom backend logic that plugs into a Wix service. For example, you can add custom pricing logic to Wix Bookings or integrate an unsupported payment provider.
Manage your site's content and data with Wix's integrated database solutions, allowing for dynamic, data-driven site experiences.
Data collections are CMS collections that let you store, query, and display structured content. You can manage collection data directly in the Wix dashboard or access it programmatically from your frontend and backend code.
External databases let you connect an external database to your site so you can work with its data through the same APIs you use with native Wix data.
Wix's built-in business solutions, including Wix Stores and Wix Bookings, are available on Studio Two sites. You can connect to them through their Data Sources when available to display and interact with their data, and extend them using service plugins to inject custom logic into their flows.
Add custom pages, modals, and plugins to the Wix site dashboard.
Dashboard pages are custom pages in the Wix site dashboard.
Dashboard modals are dialogs you can open from dashboard pages or menu plugins.
Dashboard plugins are custom widgets that fill predefined slots on Wix dashboard pages.
Dashboard menu plugins are menu items that appear in a Wix dashboard page's navigation.
Dashboard external pages are dashboard pages that load an external URL.
Use preview mode to test your code in a controlled environment without affecting the live version of your site. You can also create a dedicated test site to experiment with features and test integrations without impacting your live site.
Keep track of your site's performance and troubleshoot issues with the monitoring dashboard. Review the log entries your site's code writes on the Logs page in the site dashboard, and forward them to an OpenTelemetry endpoint for longer storage and analysis. See About Logs in Studio Two.
Last updated: 2 November 2026