Contributing to Meshery UI

UI Contribution Flow

Meshery is written in Go (Golang) and leverages Go Modules. UI is built on React and Next.js. To make building and packaging easier a Makefile is included in the main repository folder.


The following is a list of top-level frameworks, libraries, design system used in Meshery UI.

  • NextJS - Server and router
  • ReactJS - User Interface library
  • Material UI - Design System
  • BillboardJS - Charting library, used for exposing Grafana and Prometheus-collected metrics
  • CytoscapeJS - a visualization tool for canvas-based, visual topology (networks)

Meshery Server APIs

Go here for the docs.


  • Meshery provides a REST API available through the default port of 9081/tcp.
  • List of endpoints (spreadsheet) a simple, static list of REST API endpoints with short description of their purpose.
  • Swagger / Open API.
  • Collection of sets of REST API docs that Meshery server exposes to clients (like the Meshery UI).


  • Meshery provides a GraphQl API available through the default port of 9081/tcp.
  • Relay is the client used.


Wireframing / Mockups

Fill-in a community member form to gain access to community resources. You need to ask for the access to the above Figma File in Slack

Design Prologue

Meshery UI is a significant component of the value proposition Meshery offers to individuals and organizations seeking to adopt and operate a service mesh or collection of service meshes.

Design Goals

The designs in this specification should result in enabling:

  • User experience should be intuitive

    This is achieved through sensible defaults, consistency of user interaction paradigms and features that delight the user.

  • Meshery UI should simplify user management of workloads and service meshes

    Meshery UI needs to be simple, but powerful. This is achieved through intuitive layouts and predefined filters that accommodate common tasks.

  • Extensible

    Meshery UI should be a first-class component of Meshery, but also facilitate third-party integrations.

Design Objectives

The designs in this specification should result in enabling:

  • Meshery UI should be event-driven where possible.


Node Version Recommendations

We recommend to use LTS versions of node:

  • Node 16 LTS:
  • Node 18 LTS:

The script supports other node versions as well, including node15 and node17, but is recommended to use node versions above 15 and especially node LTS v18.


  • When contributing to this project, it is advisable to

    • Use eslint plugin for Visual Studio Code.

    • Disable plugins other than eslint for formatting and linting, if any.

Install UI dependencies

To install/update the UI dependencies:

make ui-setup

Build and export UI

To build and export the UI code:

make ui-build

Using this command, changes that you make are not rebuilt automatically. You will have to run this command again to rebuild the UI and see them.

Now that the UI code is built, Meshery UI will be available at http://localhost:9081 when Meshery Server is running (Read below).

To build and export the UI code and build and run Meshery Server:

make ui-server

Run Meshery Server

To start running Meshery Server locally:

make server

Now, Meshery will run on the default port http://localhost:9081.

UI Development Server

If you want to work on the UI, it will be a good idea to use the included UI development server. You can run the UI development server by running the following command:

make ui

Refer to Contributing to Meshery Server, if needed.

Make sure to have Meshery Server configured, up and running on the default port http://localhost:9081 and choose a provider to login with (visit http://localhost:9081) before proceeding to access and work on the UI server at http://localhost:3000.

Any UI changes made now will automatically be rebuilt and served in your browser.

Running Cypress integration tests

To run cypress integration tests, a convenience make target called ui-integration-tests that installs dependencies in /ui and /provider-ui folders as prerequisite and invokes ci-test-integration npm script found in /ui/package.json

make ui-integration-tests

Refer to Meshery Cypress Testing for details of how to contribute and benefit from Meshery Cypress (integration & end-to-end) testing.

Static Files, Icons and Images

The Meshery UI public folder contains static files. Its folder structure looks like this:

└── ui
    └── public
        └── static
            β”œβ”€β”€ favicon.png
            β”œβ”€β”€ fonts
            β”œβ”€β”€ img
            └── style

Images and icons used in Meshery UI need to be sourced from the public directory of images. The files written inside this directory should only end with the extensions like .svg, .png, .jpg or .jpeg. Always use vector-based graphics (.svg), unless your have extenuating circumstances.

Conventions for SVG files
  1. SVGs should be optimized and compressed.
    1. Use an online, SVG optimizer, like, to compress the file(s) to smaller size.
  2. All SVGs should have height and width properties set to 20px x 20px by default. Ensure that height and width attributes are always set in original SVG.
  3. All SVGs should have height and width included as a style prop in their React component.
  4. Always include this XML header in each SVG image:
    <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE svg>
  5. Svg can only fall under two categories, and this categories should be the name of folder
    1. white: containing white or mono-colored version of that SVG
    2. color: containing colored version of that SVG. e.g.: the Meshery logo icon folder structure looks like this:
       └── img
       └── meshery
           β”œβ”€β”€ white
           |   └── meshery-white.svg
           └── color
               └── meshery-color.svg
  6. Avoid any kind of duplicity in the versions of icons used.

For accessing the svg file as data-url, the utf8 encoding should be used in place of base64.Use encodeURIComponent on SVG data URIs. \

let svg = 'data:image/svg+xml;utf8,' + encodeURIComponent(svgFile);

Suggested Reading