optimizely-blocklisted
Install: claude install-skill tgardner18/optitech-nextjs
# Optimizely Block Authoring (this repo)
Authoring CMS blocks and sections for this Next.js + Optimizely SaaS CMS repo.
It captures the **actual conventions in the codebase**, not generic SDK docs.
> Supersedes `optimizely-model` / `optimizely-model-react` here. Those describe
> the bare SDK; this repo has a fixed four-layer + showcase + push workflow with
> seven required artifacts. Follow this skill for work under `cms/` or
> `components/blocks/`.
## Definition of done — SEVEN artifacts, together
A block is **not** complete until all seven exist and reference each other with
the **same** content-type key and slug. A half-wired block renders as nothing
(silent failure) or breaks the production build.
| # | Artifact | Path |
|---|---|---|
| 1 | Content type | `cms/content-types/OT_<Name>Block.ts` |
| 2 | Display template | `cms/display-templates/OT_<Name>Default.ts` |
| 3 | CMS adapter (server) | `cms/components/OT_<Name>Block.tsx` |
| 4 | UI component (pure React) | `components/blocks/<Name>Block.tsx` |
| 5 | Registry — **three** entries | `cms/registry.ts` (content type + display template + resolver) |
| 6 | Showcase demo | `app/(site)/showcase/blocks/[block]/page.tsx` (slug + meta + component + switch) |
| 7 | Showcase nav item | `app/(site)/showcase/config.ts` (`items` array) |
**Optional, when the block needs them:**
- **Styling helper** — `cms/styling/OT_<Name>Block.styling.ts`: maps the flat
`displaySettings` record to a typed `StyleOptions` object with default