Best way to model a page/navigation tree

[ArcoMul]

I've been experimenting with Keystone, and couldn't find an example on how to model a page tree structure.

So far I came to the following approach, curious to hear if anyone has any better/other approaches.

This enables a quick look-up based on the path property, which contains the whole pathname/url of the page, and should always be unique.

  Page: list({
    fields: {
      
      slug: text(),

      parent: relationship({ ref: "Page" }),

      path: text({
        isIndexed: "unique",
        ui: {
          itemView: {
            fieldMode: "read",
          },
        },
      }),
    },
    hooks: {
      resolveInput: async ({ context, item, inputData, resolvedData }) => {
        const slug = inputData?.slug || item?.slug || "";
        const parentId =
          inputData?.parent?.connect?.id || item?.parentId || undefined;

        // No parent, return just the slug
        if (!parentId) {
          return {
            ...resolvedData,
            path: "/" + slug,
          };
        }

        // There is a parent, combine the parent path with the page slug
        const page = await context.prisma.page.findFirst({
          where: { id: parentId },
        });
        if (!page) {
          throw Error("Parent page not found");
        }
        if (page.path === "/") {
          throw Error("Page can't have the homepage as parent page");
        }
        return {
          ...resolvedData,
          path: page.path + "/" + slug,
        };
      },
    },
  }),

Data look as follows then: