# Fields, the body, and the rich-text editor

URL: https://kywi-docs-production.up.railway.app/authoring/fields-the-body-and-the-rich-text-editor
Type: docPage

Kywi has 18 field types, and every richText field — the Body included — shares one deliberately small rich-text editor with a fixed toolbar.

A content type is built from 18 field types — text, richText, textarea, select, multiSelect, relationship, group, image, file, date, boolean, number, json, color, slug, url, email and list. Most behave the way their name suggests; richText is the one worth knowing more about, because a content type’s Body is a richText field like any other, sharing the same editor as every other one on the site.

## One editor, everywhere richText appears

The rich-text editor’s toolbar is deliberately small: paragraph text, bold, italic, a link, and headings capped at two levels. There’s no table, no underline, no text-align, and no highlight or text colour — what you see in the toolbar is genuinely the whole formatting vocabulary, not a subset hidden behind a “more” button.

## There’s no way to add an image from inside the editor

The editor can render an inline image if one is already present in the stored content, but nothing in its toolbar lets you add one — there’s no image button. A richText field is text formatting only in practice; reach for an `image` field, in a separate slot on the content type, for anything you need to show.

## multiSelect shows nothing selected when you reopen it

## A multiSelect field always looks empty on load, even when it isn’t

Opening a record with existing multiSelect choices shows the field with nothing highlighted, regardless of what was actually saved. Because the browser has no idea what was already selected, clicking any option replaces the whole selection with just that click — there’s no way to add one option while keeping the others, since you can’t see the others to keep them. Nothing in the admin shows you the stored value either: Version History’s Diff view only lists fields that differ between two saved versions, not the current record’s full stored state, so it won’t tell you what’s already selected. Treat the field as blank every time you need to change it, and re-select every option you want — not just the one you’re adding — before you save.

## Field limits are enforced on Save, not while you type

A field with a length limit doesn’t stop you from typing past it, and it doesn’t quietly truncate what you enter either — the limit is checked when you save, and a value that’s too long is rejected outright with an error rather than cut down to fit. If a save fails for no obvious reason, check whether a text field has run long.

## One malformed json field blocks the entire save

A json field accepts free text: empty is fine, but anything you do type has to parse as valid JSON. If it doesn’t, the whole record’s Save is disabled — not just that field — until the value is fixed or cleared.
