Next.js

Next.js has the most complete genko.me integration. Add List and View to App Router server components. They handle fetching, rendering, pagination, and draft previews. You do not need a Route Handler or Proxy, and the API key stays on the server.

The delivery API is REST, so you can use it with other frameworks too. With Next.js, you can skip writing the fetch logic.

Packages

@genko-me/react lists Next.js 16 or later and React 19 as peer dependencies. You can use @genko-me/sdk alone with Next.js 14 or later.

Good fit

• Server-rendered blogs, news, and case studies built with the App Router.
• Lists that need pagination. Pagination fetches the next page through a Server Action.
• Sites where editors need to review saved drafts on the live page before publishing.

Limitations

• Static export (output: "export") and the Edge runtime. Pagination uses a Server Action and cannot run in these environments. You can build lists without pagination and detail pages with SDK fetch methods.
• Pages Router. List and View require the App Router and depend on next/navigation and next/server.
• Direct browser requests. Do not pass an API key to client components. Fetch on the server.
• Writing content. The delivery API is read-only. Create and update entries in the dashboard.

Next steps

• Get started: Install and build list and detail pages
• Tutorial: Add pagination, draft previews, and webhook revalidation
• Display content with List and View: Component props
• Write your own fetch logic: Work directly with metadata and sitemaps