Rich text editor

Issue descriptions (and, in read-only/disabled mode, an integration's catalog overview copy) are edited/rendered through Tiptap, configured once in EditableMarkdown.tsx and stored as plain markdown text on the backend — there's no separate rich-content column or JSON document format, just a TEXT column holding whatever markdown Tiptap's tiptap-markdown extension serializes.

Guides, in the order you'd actually need them

Add a new Tiptap extension — worked example adding text highlighting (@tiptap/extension-highlight, not currently installed) to the editor's extension list.

The architecture in one paragraph

EditableMarkdown (resources/js/Components/Molecules/EditableMarkdown/EditableMarkdown.tsx) wraps a single useEditor() call from @tiptap/react, always mounted but toggling editable: false/true on click rather than conditionally rendering a separate read/edit component — clicking the rendered content calls startEditing() (sets editable: true, focuses the end), and losing focus (onBlur) or pressing Escape exits editing, calling onSave(markdown) only if the content actually changed (compared via tiptap-markdown's editor.storage.markdown.getMarkdown() against the last-saved value prop). The extension list — StarterKit (bold/italic/lists/headings/code/etc., with link configured not to open on click while editing), Markdown (the serializer itself, html: false so pasted/typed HTML never leaks into the stored markdown), Placeholder, TaskList/TaskItem, TableKit, and Image — is the single place that decides what formatting is possible; nothing else in the app has its own separate Tiptap configuration. A separate rendering path, react-markdown/remark-gfm (see ../architecture/01-tech-stack-and-project-structure.md), handles markdown that's never editable at all (the integrations catalog's static overview field) — don't reach for Tiptap for read-only markdown display; it's a heavier tool for a job react-markdown already does.