insites

To structure pages and forms in Insites safely, use a module-based file architecture for views and schemas, enforce page-owned data fetching, and use form callback_actions for mutations to prevent convention drift.

Handling GraphQL queries and authentication in Insites requires following strict Liquid and GraphQL conventions, enforcing audit-first validation, and implementing authorization policies to protect routes and manage data access securely.

Setting up API endpoints and CRM integrations using Insites platform rules involves organizing code within a module-aware architecture and applying strict validation guardrails to ensure all data access follows audited conventions.

Insites development requires specific file locations for layouts and partials, enforcing a module-aware architecture that dictates exact paths for views, schema, migrations, and reusable components to maintain structural integrity.

The best way to scaffold a new dashboard feature in Insites is to describe the page, data, and form behavior to the Insites skill, which guides you to the correct files, data fetching, and routing conventions step by step.