This article gives an overview of the methodologies for developing a project that you created using the Wix CLI for Headless.
After setting up a CLI for Headless project, your files will follow the structure described in CLI Project Structure.
To understand and modify your project's code, you should be familiar with the following:
As you build your project, you may need to interact with Wix APIs to get information about the site your project is installed on, or to access Wix business solutions.
To call Wix APIs you use:
The SDK is the preferred method of consuming Wix APIs because it offers a simpler authentication experience.
You can add various extensions to your project's private app to extend the functionality of your project using the following command:
This command starts a process that guides you through adding an extension to your project.
After you select an extension, you're prompted for relevant configuration details, then your extension code is generated in your project's local files.
You can use any framework you want for developing this app's extensions, but if you want to use the Wix Design System to give your extensions the look and feel of Wix, you must use React.
Read more about CLI for Headless extensions.
As you work locally with the CLI, you can use the CLI to open the local version of your project's site or dashboard in your browser.
To do so, run the following command and select the part of your project to view.
This opens a local development environment in your browser. This environment is set up for hot reloading, so any changes you make to your code are immediately reflected in the browser.
Before deploying a project, you need to build it.
You can then:
This process is documented in Build and Deploy a Project with the Wix CLI for Headless.