Fields, the body, and the rich-text editor
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.
multiSelect shows nothing selected when you reopen it
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.