Kontent.ai vs Sanity

Kontent.ai Connects Aiko AI Agent to Enterprise Apps

Kontent.ai, a headless CMS provider, introduced AI Connectors on July 7, 2026, linking its Aiko AI agent to enterprise applications including Asana, Atlassian, Notion, and Peec AI. The zero-code connectors allow Aiko to retrieve operational context, execute actions, and coordinate workflows directly within Kontent.ai's Agentic CMS. The company states the feature reduces context switching and manual coordination. More than 60 organizations already use Agentic CMS capabilities. Kontent.ai is certified under ISO/IEC 42001 for AI management systems, and the connectors are now live. The announcement follows a series of AI-related product updates, including Expert Agents and a rebranding of its conversational AI as Aiko. In April, Mark Greenaway was named CEO, replacing founder Petr Palas.

• Kontent.ai introduced AI Connectors on July 7, 2026.
• Connectors support Asana, Atlassian, Notion, and Peec AI.
• The connectors are zero-code and live in the product.

The CMS Is Dead. Long Live Content Operations.

In this podcast episode, Sanity CEO Magnus Hillestad discusses why the CMS industry has been solving the wrong problem for a decade. He argues that content should be treated as core business infrastructure, not a marketing feature. With AI agents now reading, writing, and distributing content, real-time, machine-readable content is essential. Hillestad highlights that velocity is the main reason companies leave legacy platforms, and discusses the rise of Answer Engine Optimization (AEO) and agent orchestration in content operations. He also mentions Sanity's MCP server now includes a tool for agents to report friction automatically. The content reflects a shift from traditional CMS to content operations, where AI agents become primary users.

• Sanity CEO Magnus Hillestad argues that the CMS industry has been solving the wrong problem for a decade.
• Content should be treated as core business infrastructure, not a marketing feature.
• AI agents are increasingly reading, writing, and distributing content, requiring machine-readable content.

Studio SDK integration, CLI asset uploads and token expiry, and presentation and Vision fixes v6.10.0 Sanity Studio

Sanity released multiple product updates in August 2026, including a major Sanity Studio v6.10.0 with SDK integration, JavaScript Client v8.0.0 with Node 22+ ESM-only support, new Sanity Context package, and numerous fixes across Studio, MCP server, Media Library, and React App SDK.

How to Scope a Next.js Project Before Coding

This guide outlines five essential things to define before starting a Next.js project to avoid budget and timeline overruns: a complete page inventory, an explicit CMS decision, a detailed list of third-party integrations, a performance budget, and a timeline with task-level estimates. The author recommends capturing every URL and render strategy, confirming CMS choice (Sanity is suggested as a default with GROQ noted), naming owners for each integration (analytics, forms, search, auth, video, e‑commerce, consent), and setting Core Web Vitals and bundle size targets. The post also gives per-task time estimates and example total durations for common configurations (e.g., a 12-page marketing site with Sanity, SendGrid, and GA4 typically 4–6 weeks).

• The author prescribes five scoping items before starting: page inventory, CMS decision, integrations list, performance budget, and timeline.
• Sanity is suggested as the default CMS; the post notes Sanity's Growth plan costs $15/month per seat above the free-tier limit and that GROQ is its query language.
• Recommended integration categories include Analytics (GA4, Plausible, Vercel Analytics), Forms & Email (SendGrid, Mailchimp, Loops), Search (Algolia), Authentication, Video (Mux), and E‑commerce (Shopify, Stripe).