Ridu APIs, package by package.

The ergonomic application facade for config, startup, and access decisions.

Application contracts and the operation runtime behind the root facade.

Type-safe field builders and presentation options. Incompatible options fail at Go compile time; semantic issues are reported by ridu.Resolve.

Immutable filters, validated document paths, stable sorting, and relationship population controls.

The immutable generated schema manifest, stable identifiers, and advanced generator/plugin contracts.

Advanced adapter contracts for transactional documents, auth, preferences, locks, publishing, uploads, and durable tasks.

Object-storage contracts used by upload collections. Implement this package only when the official local and S3 backends do not fit.

Advanced, database-independent vocabulary for immutable and reviewable migration artifacts.

Optional public import boundary for normalized Payload CMS exports; source-specific database extraction is deliberately out of scope.

Advanced stable REST wire envelopes shared by the HTTP runtime, generators, SDK, admin, and transport tests.

Stable backend conformance tests for third-party compiled Ridu plugins.

Reusable behavioral qualification suites for Ridu store adapters.

The official PostgreSQL store, safe development schema sync, and immutable production migration runner.

The official embedded SQLite store and its immutable, reversible migration lifecycle.

The official replica-set MongoDB store, additive development index synchronization, and immutable forward-only migration lifecycle.

Durable filesystem object storage for development and single-host deployments.

Dependency-free S3-compatible object storage with SigV4 requests and signed private reads.

An optional manifest-generated GraphQL transport over Ridu’s operation engine; importing it is what links the GraphQL runtime.

An optional authenticated, read-only Model Context Protocol transport over explicitly selected Ridu content.

A paired, versioned Lexical field with authoring for portable content, references, uploads, and blocks.

Payload-familiar search metadata fields, authenticated draft-aware generators, and a paired Svelte admin.

Payload-familiar dynamic form definitions, server-validated submissions, notifications, uploads, and payment callbacks.

The statically bundled Svelte/Lexical half of the rich-text plugin.

The statically bundled Svelte authoring half of the official SEO plugin.

Framework-neutral public form helpers plus a separately exported static admin pairing.

The generated-contract-aware Fetch client for browser and server applications.

Generated wire contracts and runtime guards shared by the SDK and admin.

Static Svelte 5 extension contracts for generated admins and plugin packages.

Build-time Vite, Svelte 5, and UnoCSS conventions for generated admins and plugin libraries.

Shared Svelte 5 interaction primitives and class composition for the admin and static plugins.

The framework-owned Svelte admin mount contract and public admin client surface.

Typed admin translations, language negotiation, plurals, and Intl formatting.

Programmatic Node launcher for invoking the platform-specific Ridu CLI binary.

The implemented project lifecycle: scaffolding, generation, migrations, development, checks, builds, diagnostics, and static plugin management.