Links in rich text​

Rich text gained a link mark, so a run of text can now carry a hyperlink end to end — from the TipTap editor through storage, validation, and both delivery projections.

The mark sits alongside the existing formatting marks and adds two fields:

{ "type": "link", "href": "/about", "title": "About us" }

• href is required. It must be an absolute http/https URL, a mailto:/tel: link, or a relative path. Unsafe schemes like javascript: are rejected on write, and sanitized again at render time as defense in depth.
• title is optional and maps to the anchor's title attribute.

The html projection renders <a href="…">, adding rel="noopener noreferrer" on external links (and a title attribute when present). This works identically on the GraphQL and REST delivery paths. The HTML-paste cleaner (from-html) preserves anchors, so pasting from Word / Google Docs keeps links intact.

The href is a plain string today; the AST shape leaves room for a future entry-reference link variant without breaking stored content.

React​

@krios/react's KriosRichText handles the link mark out of the box — the default renderer receives href + optional title, sanitizes the href, and adds rel="noopener noreferrer" on external links. Override it like any other mark renderer for full control.

See Rich Text for the full AST reference.

isLocalizable is now immutable once a field has content​

Shared and per-locale values use different storage keys, so flipping isLocalizable after a field already has data would orphan the existing values. The field-update API now guards against this: changing the flag once any value has been written returns 409 is_localizable_immutable. Set it correctly at field creation time.

isSortable and isFilterable remain mutable. See Flags for the full matrix.

Localized altText / title / description on MediaAsset​

The GraphQL MediaAsset type now exposes the asset's locale overlay directly:

type MediaAsset {
  # …
  altText: String       # resolved from the MediaAssetLocale overlay
  title: String         # for the request locale
  description: String
}

These resolve against the request locale — the containing entry's locale for an embedded media field, the link's parent locale for a link asset, or the new locale argument on the top-level asset(id, locale) query. When no overlay row exists for that locale, the field is null. Batched through a DataLoader, so selecting it across many assets stays a single query.

This makes the asset the single, DRY source of alt text — you no longer need a sibling …Alt field on every media field, and the text localizes with the asset. The REST asset endpoint (media/{id}?locale=) continues to merge the same overlay.

krios types generate now includes these fields on the generated MediaAsset interface.

Inline rich-text images render with a resolved src​

embeddedAsset nodes in a rich-text body now render as a real <img src="…" alt="…"> in the delivery html — the CDN URL is resolved server-side on both the GraphQL and REST delivery paths. Previously the <img> came back without a src and silently failed to load, which meant inline images had to be rendered from the raw AST by hand.

embeddedEntry nodes are unchanged: they still render as a <div data-krios-entry-id="…" data-krios-content-type="…"> placeholder for the client to hydrate. So inline images now Just Work, and only embedded entries need a custom component.

See Media and Rich Text for details.

What's Included​

• Content modeling with 11 field types + custom field types
• Content tree with folders as content types
• GraphQL and REST delivery APIs
• Multi-site, multi-tenant, multi-environment
• Localization with per-field locale control
• TipTap rich text editor
• Media management with Supabase CDN
• Preview with signed tokens
• Configurable workflows and approval chains
• Translation workflows
• Advanced search with Meilisearch
• Real-time collaboration
• Governance intelligence
• And much more

Read the full documentation →