CMS integration

Connect publishing models to wallet-aware applications without mixing editorial fields with authorization logic. This reading path spans architecture, protected delivery, plugin evaluation, AI feature access, and headless content modeling. Start by defining the reader task, then choose the guide matching the component your team owns.

A useful integration brief identifies public content, protected resources, trusted services, and the fields exchanged between them. Keep those responsibilities explicit when changing the theme, adding another network, or replacing a provider.