DEV Community

Nuco Z
Nuco Z

Posted on

Building a Small Static Game Wiki with Next.js and Cloudflare Workers

#gamedev #cookierun #gamechallenge

CookieRun Classic Wiki guide hub

I recently put together a small static guide hub for CookieRun Classic: CRClassic.wiki. It is a simple content site, but the deployment path had a few details that are easy to miss when combining Next.js static export, Cloudflare Workers Static Assets, sitemap generation, and game-guide SEO.

This is a short technical note on what ended up mattering.

The site shape

The site is not an app dashboard. It is a focused information hub with separate pages for player intent:

  • codes and redeem steps
  • beginner route
  • cookie, pet, and treasure tier pages
  • PC setup
  • reroll and meta notes
  • a central wiki hub

CookieRun Classic beginner guide preview

That split helps because each URL answers a different question. A player searching for a redeem flow does not need to land on the same page as someone comparing Cookie upgrades.

Static export was the right fit

For this kind of site, static output keeps the deployment simple:

// next.config.mjs
const nextConfig = {
  output: 'export',
  images: {
    unoptimized: true,
  },
}

export default nextConfig
Enter fullscreen mode Exit fullscreen mode

The Cloudflare Workers config points directly at the generated out folder:

{
  "name": "cpclassic",
  "compatibility_date": "2026-07-01",
  "assets": {
    "directory": "./out",
    "html_handling": "auto-trailing-slash",
    "not_found_handling": "404-page"
  }
}
Enter fullscreen mode Exit fullscreen mode

The small metadata details mattered

The site needed normal page metadata, but also page-specific Open Graph images so each guide has a relevant preview instead of one generic logo.

CookieRun Classic cookie tier preview

A few details I made sure to include:

  • canonical URLs for every route
  • robots.txt and sitemap.xml
  • max-image-preview: large for Google image previews
  • page-specific og:image and Twitter card images
  • a real favicon instead of relying only on 32px PNG files

The public sitemap is here: https://crclassic.wiki/sitemap.xml

Content pages need more than lists

For game-guide pages, a plain tier table is rarely enough. The more useful structure is:

  • who should use this option
  • when to upgrade it
  • when to stop investing
  • what mistakes to avoid
  • what related page to read next

CookieRun Classic treasure upgrade preview

That is the approach I used on the Cookie Run Classic Tier List: the page includes rankings, but the real value is upgrade logic and account-stage guidance.

Takeaway

For a small wiki, the technical stack can stay boring. The hard part is making each page answer a real search intent and making sure crawlers can clearly see the URL, canonical, sitemap entry, image preview, and internal links.

If you are building a similar static guide hub, I would start with the content architecture first, then wire the metadata and deployment around that structure.

Top comments (0)