Beta . Ortha CMS is in public beta. Every plan is free until it ends.
Features Ortha CMS on GitHub

The rich-text editor

Rich text plugin @orthacms/wysiwyg-admin

What the editor can do, and the structural checks it runs while you write rather than after you save.

Documents 0.13.1 Updated Edit this page Report a problem

On this page

Since 0.12.0 a rich-text field is edited in place, in the form: click it and the caret lands in the text. The formatting toolbar appears once the field has focus, and a long body scrolls inside the field instead of pushing the rest of the form down.

Expand, at the field’s top-right corner, opens the full editor over the record’s form, for a long sitting.

  • Back to fields returns to the form, with the caret back in the field.
  • If you can only read the record, the field shows its content as it reads, and View opens the same full view to read it.
  • Ctrl+M moves focus out of the text to the close button — useful inside a table or list, where Tab is taken.
  • Pasted text drops its source’s colours and font sizes.

What it can do

GroupControls
TextParagraph, headings 1–4, text size, bold, italic, underline, strikethrough, inline code, clear formatting
ColourText colour and highlight
LayoutAlignment, bulleted and numbered lists, quote, divider
BlocksCallouts (note, success, warning, danger), tables, columns, code blocks
LinksInsert and edit, with the link text
LanguageLanguage of this passage…
MediaImages and video, resizable

Adding images and video

Under Insert:

  • Media Library… — pick an existing file.
  • Upload files… — upload and insert.
  • Image from a URL… / Video from a URL… — from anywhere.

A library image is inserted at its preview size, with its alt text copied in. From then on the alt text belongs to this image — edit it on the image. Changing the file’s alt text in the library later does not update text that already contains it.

It checks as you write

The editor shows the same structural problems the server enforces, while you can still fix them:

FindingBlocks a save
A heading that skips a levelYes
A heading above the body’s own top levelYes
An empty headingYes
A table with no header cells and no captionYes
A link with no textYes
A language marker nothing can readYes
Link text that says nothing about where it goes (“click here”)No — advice

Each finding names the accessibility guideline it comes from. You see the advice too, not only the errors — so you can fix things before they block you.

Marking the language of a passage

Select text → Language of this passage… → choose the language. Screen readers then pronounce that quote correctly.

If a whole field is in another language, your developers can mark the field itself.

Older content

Text written before the current editor opens normally. The first save converts it to the current format — nothing to do on your side.

Plain-text fields

Some fields that hold markup on purpose (a snippet, an email template) are set up by developers as a plain text box instead of this editor, so formatting is never rewritten. See rich text.

No collaborative editing

One person edits a record at a time — no live co-editing, no presence indicators. If two people save the same entry, the last save wins.

You are told, though: someone else’s save never replaces your unsaved text on screen. A notice says the record changed, and the version your save replaces stays in history. See the entry editor.