Get to know our frameworks

Select an app template built on your preferred framework.

Build apps on our native app editor. Use drag and drop elements, Velo code and Wix APIs to develop custom features.

Streamline your app development process with the Wix CLI. Get a familiar developer experience with minimal setup and configuration.

Take full control over your app's tech stack, deployment, and hosting.

App templates

Wix Blocks templates

Wix CLI templates

Self-hosted templates

Kickstart your app development with templates built on your preferred Wix developer tool. Browse templates for practical foundation and get to know the Wix ecosystem.

Wix App Templates for Developers

This example apps can be used as a starting point for building your own app, for concrete examples of how to use Wix framework, or for inspiration.

Choose a template.<0 />Build an app.

Browse by:

How to build it step by step:

This template is built with:

Read how this template was built, step by step.

How we built this template

Deployment instructions:

Choose a package manager and run the command in your terminal.

Copy command

Before you get started, make sure you have the following:

Prerequisite steps

Get started with Wix CLI

Begin by setting up your Next.js project with your preferred hosting platform.

Select your hosting service

Start the deployment flow and set up your template repo on Netlify. After you finish set up, come back here and add your Netlify custom domain.

Copy the code from our Git repo to deploy your app on any platform that supports Next.js.

Start the deployment flow and set up your template repo on Vercel. After you finish set up, come back here and add your Vercel generated URL.

Add the base URL and give your app a name.

App details

Go to the app dashboard and test your app to ensure a smooth integration within the Wix ecosystem. <0>Learn more about app checks and testing</0>

Define your environment

Terminal

Related templates

Note

Warning

Your app name will be used as the namespace suffix.

Name your app to generate a namespace. This lets you refer to your app in code later on.

Go Headless

Build Apps

Client

API Preview

Ricos

Develop Websites

REST

Velo

GraphQL (Alpha)

# About Wix Restaurants Catalogs

> **Note:** This API only works with the original Wix Restaurants Menus app. Call [GetAppInstance](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::5a829a3f-423e-484e-80c5-b70320bf9383slug::get-app-instance*fallback::https://dev.wix.com/docs/rest/api-reference/app-management/apps/app-instance/get-app-instance) to confirm that the app named “restaurants_menus” is installed on the site.

With Wix Restaurants Catalogs, site owners can manage individual catalogs for each of their restaurant locations.

The Catalogs API allows your app to:

* Retrieve catalogs
* Read and manage menus, sections, dishes, variations, and discounts
* Use draft catalogs to synchronize updates

You can read more about setting up and managing multiple locations for a business with the [Locations API](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::1a7dfd1e-acc2-42cb-bf24-298cbb9858c5slug::introduction*fallback::https://dev.wix.com/api/rest/business-info/locations/introduction).


## Terminology


* **Catalog:** Collection of menus and discounts available in a specific location.
* **Draft Catalog:** Allows you to publish multiple changes to a catalog at the same time.
* **Menu:** Catalogs are made up of menus. For example "Breakfast", "Lunch", and "Dinner" menus.
* **Section:** Menus are made up of sections. For example "Appetizers", "Entrees", and "Desserts" sections.
* **Item:** Anything that customers can buy in the restaurant. Can be of type dish or variation.
    + **Dish:** Item that appears in a section of a menu.
    + **Variation:** Item that doesn't appear in a section on its own, only as a choice for a dish.
* **Choice:** Item that customers can choose to modify a dish. Both item types variation and dish are supported.
    + **Available Choices:** All possible choices for a dish.
    + **Default Choices:** The choices for a dish that are selected by default.
    + **Selected Choices:** The choices a customer has selected for a dish.
* **Dish Option:** Type of the choice. Can be an extra, selection, or deselection.
    + **Extra:** Item that customers can add to a dish. For example a topping. Customers can add multiple extras per dish.
    + **Selection:** Item that customers can select. For example a dish size. Customers can choose only a single selection per dish.
    + **Deselection:** Item that customers can remove from a dish. For example a specific ingredient. Customers can remove multiple deselections per dish.
* **Label:** Information about the ingredients and constituents of a dish. For example "spicy", "hot", "vegan", "gluten-free", or "organic".
* **Discount:** Can be an amount or percentage. Applies to a catalog, section, or dish. Customers may need to enter a coupon code to receive the discount.


## Limitations

* Each location has a single catalog.
* A section belongs to a single menu.
* You can create discounts for catalogs, sections, or dishes. You can't create a discount that applies to a menu.
* Currently, the [Catalog Changed](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::ca2697c5-d1b9-4737-a2d9-bb4e65238c77slug::catalog-changed*fallback::https://dev.wix.com/api/rest/wix-restaurants/catalogs/catalogs/catalog-changed-webhook) webhook doesn't return information about what has changed. In order to update an external POS upon changes to a Wix Restaurants catalog you may need to create your own logic to identify the changes.