A Company Website Demo using Next.js 16 and DatoCMS

This example showcases a TypeScript Next.js 16 website with App Router (app) — using DatoCMS as the data source.

Next.js 16 Features

This demo takes advantage of the latest Next.js 16 features.

It uses GraphQL CodeGen to type all of the requests coming from DatoCMS automatically: See how it works here

DatoCMS Integration

This project uses the official @datocms/cda-client package for querying the DatoCMS Content Delivery API. This lightweight TypeScript client provides:

• Full TypeScript support with TypedDocumentNode
• Automatic retry on rate limits
• Support for draft content previews
• Seamless integration with Next.js caching

Additionally, react-datocms is used for real-time updates, responsive images, and SEO metadata handling.

Demo

Have a look at the end result live:

https://company-website-demo-preview.vercel.app/

How to use

Quick start

1. Create an account on DatoCMS.

2. Make sure that you have set up the Github integration on Vercel.

3. Let DatoCMS set everything up for you clicking this button below:

Local setup

Once the setup of the project and repo is done, clone the repo locally.

Set up environment variables

In your DatoCMS' project, go to the Settings menu at the top and click API tokens.

Then click Read-only API token and copy the token.

Next, copy the .env.example file in this directory to .env (which will be ignored by Git):

1
cp .env.local.sample .env.local

and set the DATOCMS_READONLY_API_TOKEN variable as the API token you just copied.

Also then set a secret token that is being used for WebPreviews, SEO Previews and Cache invalidation:

1
URL=http://localhost:3000
2
SEO_SECRET_TOKEN=superSecretToken
3
DRAFT_SECRET_TOKEN=superSecretToken
4
CACHE_INVALIDATION_SECRET_TOKEN=superSecretToken

Run your project locally

1
pnpm install
2
pnpm dev

Your blog should be up and running on http://localhost:3000!

VS Code

It's strongly suggested to install the GraphQL: Language Feature Support extension, to get autocomplete suggestions, validation against schema, and many more niceties when working with your GraphQL queries.