Ridu APIs, package by package.

Configure a Ridu application, start its server, and define access rules.

Application settings and server APIs, also available from the root ridu package.

Define fields, add validation and permissions, customize their inputs, and reuse field groups.

Read values in field callbacks, report validation errors, and return changes from hooks.

Build filters, refer to fields by path, sort results, and choose which relationships to load.

Inspect Ridu's resolved collections and fields, and work with resource, field, and locale identifiers.

Build and read document values for the local API and hooks. This package also defines the interfaces database adapters implement.

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 statically bundled admin GraphQL playground paired with the Go GraphQL plugin.

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

SvelteKit integration: direct browser requests to Ridu, server rendering, and one session owner.

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

Build custom Svelte components, register admin plugins, and work with field forms.

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.