Your project's description...
This project renders AEM Edge Delivery content through Next.js App Router + React Server
Components instead of the native client-side aem.js decoration. EDS remains the headless
content/authoring source (Docs/DA, sidekick, .page/.live unchanged); a Cloudflare Worker
fronts EDS and renders at the edge. See DEPLOYMENT.md for the full picture.
- Blocks live in
/blocks/<name>/:Name.jsx(the React component) +name.js(entry shim)name.css. The registry inlib/registry.jsmaps block name → component.
- The EDS parse layer is in
lib/eds/(fetch → parse → render). - Requires Node 18+ (
nvm use 22). Run locally withnpm run dev; deploy withnpm run deploy:cf.
Status: spike —
hero,cards, andcolumnsare converted. Other blocks still have their nativeaem.jsdecorate functions and render as placeholders until ported.
Before using the aem-block-collection, we recommand you to go through the documentation on https://www.aem.live/docs/ and more specifically:
- Developer Tutorial
- The Anatomy of a Project
- Web Performance
- Markup, Sections, Blocks, and Auto Blocking
- AEM Block Collection
npm inpm run lint- Create a new repository based on the
aem-block-collectiontemplate and add a mountpoint in thefstab.yaml - Add the AEM Code Sync GitHub App to the repository
- Install the AEM CLI:
npm install -g @adobe/aem-cli - Start AEM Proxy:
aem up(opens your browser athttp://localhost:3000) - Open the
{repo}directory in your favorite IDE and start coding :)