@djangocfg/nextjs 2.1.537 → 2.1.539

package/README.md

@@ -23,7 +23,7 @@
 
 ## Features
 
-- **Page Metadata + OG Images** — one factory for complete page metadata; static or dynamically-rendered OG images via Django's `django_ogimage` (`@djangocfg/nextjs/og-image`)
+- **Page Metadata + OG Images** — one factory for complete page metadata: titles, canonical + hreflang, OpenGraph, Twitter, icons (`@djangocfg/nextjs/og-image`)
 - **i18n** — full next-intl integration with routing, middleware, and components
 - **PWA** — zero-config service worker and manifest
 - **Base Next.js Config** — reusable `createBaseNextConfig()` factory for monorepos
@@ -391,8 +391,7 @@ export const GET = createHealthHandler({
 
 One factory per app builds complete page `Metadata` (title, openGraph, twitter,
 canonical + hreflang, icons). The OG image is chosen by a single `og` field —
-static brand image by default, dynamic title-rendered card on demand. No Edge
-Runtime, no `@vercel/og`:
+the static brand image by default, or an exact URL:
 
 ```tsx
 // app/_core/metadata.ts — bind once
@@ -407,11 +406,13 @@ export const createMetadata = makeMetadataFactory({
 
 // landing page → static brand image (default)
 export const metadata = createMetadata({ title: 'Pricing', path: '/pricing' })
-// content page → render the title onto the card
-export const metadata = createMetadata({ title: post.title, path, og: 'dynamic' })
+// content page with its own image
+export const metadata = createMetadata({ title: p.name, path, og: { image: p.image } })
 ```
 
-The dynamic URL is resolved automatically from `NEXT_PUBLIC_MEDIA_URL` → `NEXT_PUBLIC_API_URL` → `NEXT_PUBLIC_SITE_URL`. Django renders and caches the PNG — no Edge Runtime or `@vercel/og` required.
+For a card rendered per page, add an `opengraph-image` route — Next.js finds it
+by filename and its output overrides whatever the factory set, so the factory
+has no "dynamic" case of its own.
 
 ### Navigation Utilities
 
@@ -461,7 +462,7 @@ import { RedirectPage } from '@djangocfg/layouts/components/RedirectPage';
 | `@djangocfg/nextjs/pwa/worker` | Service worker creation helpers |
 | `@djangocfg/nextjs/sitemap` | Sitemap generation with i18n hreflang support |
 | `@djangocfg/nextjs/health` | Health check handlers |
-| `@djangocfg/nextjs/og-image` | Page metadata factory + static/dynamic OG images for Django's `django_ogimage` |
+| `@djangocfg/nextjs/og-image` | Page metadata factory — titles, canonical + hreflang, OpenGraph, Twitter, icons |
 | `@djangocfg/nextjs/navigation` | Route definitions, menu generation, navigation helpers |
 
 ## API Reference
@@ -623,17 +624,16 @@ createHealthHandler({
 
 ### Page Metadata + OG Image
 
-`@djangocfg/nextjs/og-image` builds complete page metadata and OG images for
-Django's `django_ogimage` renderer. No Edge Runtime, no `@vercel/og`, no JSX
-templates — Django renders and caches the PNG.
+`@djangocfg/nextjs/og-image` builds complete page metadata: title templating,
+canonical + hreflang alternates, OpenGraph, Twitter cards and icons.
 
 See [`src/og-image/README.md`](./src/og-image/README.md) for full docs (the `og`
-axis, `SiteMetaConfig`/`PageMeta` fields, URL resolution, deployment examples).
+axis, `SiteMetaConfig`/`PageMeta` fields).
 
 #### `makeMetadataFactory(config)` — recommended
 
 Binds a `SiteMetaConfig` once; returns a per-page factory. The OG image is set by
-the single `og` field: `'static'` (default) · `'dynamic'` · `{ render }` · `{ image, alt? }`.
+the single `og` field: `'static'` (default) · `{ image, alt? }`.
 
 ```tsx
 import { makeMetadataFactory } from '@djangocfg/nextjs/og-image'
@@ -643,23 +643,21 @@ export const createMetadata = makeMetadataFactory({
   ogImage: '/static/ogimage.png', locales: LOCALES,
 })
 
-export const metadata = createMetadata({ title: 'About', path: '/about' })          // static
-export const metadata = createMetadata({ title: post.title, path, og: 'dynamic' })  // rendered title
+export const metadata = createMetadata({ title: 'About', path: '/about' })      // brand image
+export const metadata = createMetadata({ title: p.name, og: { image: p.image } })
 ```
 
-#### Low-level (escape hatches)
+#### Per-page rendered cards
 
-`withOgImage(metadata, params)` merges a dynamic OG image into existing metadata;
-`createOgMetadata(params)` returns the `{ openGraph, twitter }` fragment;
-`buildOgUrl(params)` returns the raw URL string; `resolveOgImage(spec, …)` is the
-`OgSpec` decision point. Most pages use `createMetadata` and never touch these.
+Use Next.js's `opengraph-image` file convention. It is discovered by filename
+and overrides metadata, so this package needs no support for it — and offering
+a second route to the same tag would only create a conflict.
 
-```tsx
-import { buildOgUrl } from '@djangocfg/nextjs/og-image'
-const url = buildOgUrl({ title: 'Hello', preset: 'DARK_BLUE' })
-```
+#### Low-level (escape hatches)
 
-**URL resolution** (`NEXT_PUBLIC_MEDIA_URL` → `NEXT_PUBLIC_API_URL` → `NEXT_PUBLIC_SITE_URL` → relative).
+`resolveOgImage(spec, staticUrl, fallbackTitle)` is the `OgSpec` decision point;
+`extractTitle(metadata)` reads a plain title out of Next.js's title shapes. Most
+pages use `createMetadata` and never touch these.
 
 ### Navigation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@djangocfg/nextjs",
-  "version": "2.1.537",
+  "version": "2.1.539",
   "description": "Next.js server utilities: sitemap, health, OG images, contact forms, navigation, config",
   "keywords": [
     "nextjs",
@@ -149,9 +149,9 @@
     "ai-docs": "tsx src/ai/cli.ts"
   },
   "peerDependencies": {
-    "@djangocfg/devtools": "^2.1.537",
-    "@djangocfg/i18n": "^2.1.537",
-    "@djangocfg/ui-core": "^2.1.537",
+    "@djangocfg/devtools": "^2.1.539",
+    "@djangocfg/i18n": "^2.1.539",
+    "@djangocfg/ui-core": "^2.1.539",
     "next": "^16.2.2"
   },
   "peerDependenciesMeta": {
@@ -170,11 +170,11 @@
     "semver": "^7.8.5"
   },
   "devDependencies": {
-    "@djangocfg/devtools": "^2.1.537",
-    "@djangocfg/i18n": "^2.1.537",
-    "@djangocfg/layouts": "^2.1.537",
-    "@djangocfg/typescript-config": "^2.1.537",
-    "@djangocfg/ui-core": "^2.1.537",
+    "@djangocfg/devtools": "^2.1.539",
+    "@djangocfg/i18n": "^2.1.539",
+    "@djangocfg/layouts": "^2.1.539",
+    "@djangocfg/typescript-config": "^2.1.539",
+    "@djangocfg/ui-core": "^2.1.539",
     "@types/node": "^25.9.5",
     "@types/react": "19.2.15",
     "@types/react-dom": "19.2.3",