Creating List Pages

Setup

Info

This guide assumes you have a CmsPlugin with an Article entity, as covered in the Extending the Dashboard: Plugin Setup guide.

List pages can be easily created for any query in the Admin API that follows the PaginatedList pattern.

For example, the articles query of our CmsPlugin looks like this:

Graphql

type ArticleList implements PaginatedList {    items: [Article!]!    totalItems: Int!}extend type Query {    articles(options: ArticleListOptions): ArticleList!}

List Page Example

First we'll create a new article-list.tsx file in the ./src/plugins/cms/dashboard directory:

src/plugins/cms/dashboard/article-list.tsx

import {    Button,    DashboardRouteDefinition,    ListPage,    ActionBarItem,    DetailPageButton,    Link,} from '@vendure/dashboard';import { PlusIcon } from 'lucide-react';// This function is generated for you by the `vendureDashboardPlugin` in your Vite config.// It uses gql-tada to generate TypeScript types which give you type safety as you write// your queries and mutations.import { graphql } from '@/gql';// The fields you select here will be automatically used to generate the appropriate columns in the// data table below.const getArticleList = graphql(`    query GetArticles($options: ArticleListOptions) {        articles(options: $options) {            items {                id                createdAt                updatedAt                isPublished                title                slug                body                customFields            }            totalItems        }    }`);const deleteArticleDocument = graphql(`    mutation DeleteArticle($id: ID!) {        deleteArticle(id: $id) {            result        }    }`);export const articleList: DashboardRouteDefinition = {    navMenuItem: {        sectionId: 'catalog',        id: 'articles',        url: '/articles',        title: 'CMS Articles',    },    path: '/articles',    loader: () => ({        breadcrumb: 'Articles',    }),    component: route => (        <ListPage            pageId="article-list"            title="Articles"            listQuery={getArticleList}            deleteMutation={deleteArticleDocument}            route={route}            customizeColumns={{                title: {                    cell: ({ row }) => {                        const post = row.original;                        return <DetailPageButton id={post.id} label={post.title} />;                    },                },            }}        >            <ActionBarItem>                <Button render={<Link to="./new" />}>                    <PlusIcon className="mr-2 h-4 w-4" />                    New article                </Button>            </ActionBarItem>        </ListPage>    ),};

Let's register this route (and we can also remove the test page) in our index.tsx file:

src/plugins/cms/dashboard/index.tsx

import { defineDashboardExtension } from '@vendure/dashboard';import { articleList } from './article-list'; // [!code highlight]defineDashboardExtension({    routes: [        articleList, // [!code highlight]    ],});

Note

After adding new Dashboard files to your plugin, you'll need to re-start the dev server for those files to be picked up by Vite:

q # to stop the running dev servernpx vite # to restart

The ListPage Component

The ListPage component can be customized to your exact needs, such as:

Setting the columns which are visible by default
Setting the default order of the columns
Defining bulk actions ("delete all selected" etc.)

See the ListPage component reference for an explanation of the available options.

Customizing Columns

It is common that you will want to customize the way certain columns are rendered. This is done using the customizeColumns prop on the ListPage component.

By default, an appropriate component will be chosen to render the column data based on the data type of the field. However, in many cases you want to have more control over how the column data is rendered.

Tsx

<ListPage    pageId="collection-list"    listQuery={collectionListDocument}    customizeColumns={{        // Use `meta.disabled` to completely exclude a column from the table,        // including the column visibility toggle. This is useful when you need        // to fetch certain fields for use in custom cell renderers, but don't        // want those fields to appear as their own columns.        productVariantCount: {            meta: { disabled: true },        },        // The key "name" matches one of the top-level fields of the        // list query type (Collection, in this example)        name: {            meta: {                // The Dashboard optimizes the list query `collectionListDocument` to                // only select field that are actually visible in the ListPage table.                // However, sometimes you want to render data from other fields, i.e.                // this column has a data dependency on the "children" and "breadcrumbs"                // fields in order to correctly render the "name" field.                // In this case, we can declare those data dependencies which means whenever                // the "name" column is visible, it will ensure the "children" and "breadcrumbs"                // fields are also selected in the query.                dependencies: ['children', 'breadcrumbs'],            },            header: 'Collection Name',            cell: ({ row }) => {                const isExpanded = row.getIsExpanded();                const hasChildren = !!row.original.children?.length;                return (                    <div                        style={{ marginLeft: (row.original.breadcrumbs?.length - 2) * 20 + 'px' }}                        className="flex gap-2 items-center"                    >                        <Button                            size="icon"                            variant="secondary"                            onClick={row.getToggleExpandedHandler()}                            disabled={!hasChildren}                            className={!hasChildren ? 'opacity-20' : ''}                        >                            {isExpanded ? <FolderOpen /> : <Folder />}                        </Button>                        <DetailPageButton id={row.original.id} label={row.original.name} />                    </div>                );            },        },    }}/>

Was this chapter helpful?

Report Issue

Edited Mar 23, 2026·View source