Ai12z.Optimizely.Cms 0.1.0

Ai12z.Optimizely.Cms

NuGet package for integrating ai12z with Optimizely CMS (formerly Episerver). Provides:

• Real-time content sync — hooks publish, move-to-trash, and delete events on pages and PDF media, sending payloads to the ai12z connector service automatically
• Admin settings page — configure everything from a built-in admin UI at /ai12z-sync, no appsettings.json editing required
• Full initial sync — one-click full-site sync that reuses the same extraction pipeline as real-time events, so every page and PDF is indexed under a single stable identifier
• Resilient delivery — outbound HTTP uses a named client with a 30s timeout and exponential-backoff retries

Requirements

• Optimizely CMS 13 (EPiServer.CMS 13.x)
• .NET 10
• ai12z account with an Optimizely connector configured

Installation

dotnet add package Ai12z.Optimizely.Cms

Setup

1. Program.cs / Startup

Register the connector services in your Optimizely site's DI container:

builder.Services.AddAi12zOptimizely();

No other code changes are needed — no layout changes and no manual endpoint registration. The connector's controllers ship as an MVC application part and are auto-discovered by your existing app.MapControllers() call. The Ai12zModule initializable module wires up the content publish/move/delete events automatically.

2. Configure in the admin UI

Browse to /ai12z-sync on your running site (e.g. https://your-site.com/ai12z-sync).

• Endpoint URL — from the ai12z portal Optimizely connector page (includes Connector ID and Project ID)
• Connector API Key — generated via "Manage Keys" on the connector page
• Content Sync Enabled — toggle on

Settings are persisted in the Optimizely Dynamic Data Store (database) — no appsettings.json entries required.

3. Initial content sync

Trigger a full-site sync from the admin UI, or call the endpoint directly:

# Full sync of all pages + PDF media
curl https://your-site.com/api/sync/full

# Check sync status
curl https://your-site.com/api/sync/status

After the initial sync, content is synced automatically on publish, move-to-trash, and delete.

How it works

• Publishing the root/start page schedules a full-site sync (after a short, configurable delay) so large structural changes propagate in one pass.
• Publishing any other page or a PDF media item sends an incremental published event.
• Moving a page/PDF to the wastebasket or permanently deleting it sends an unpublished event so the index stays in sync.

Documentation

Full setup guide: https://docs.ai12z.net/docs/connectors/optimizely