Lexxy

A modern rich text editor for Rails.

• Built on top of Lexical, the powerful text editor framework from Meta.
• Good HTML semantics. Paragraphs are real <p> tags, as they should be.
• Markdown support: shortcuts, auto-formatting on paste.
• Real-time code syntax highlighting.
• Create links by pasting URLs on selected text.
• Configurable prompts. Support for mentions and other interactive prompts with multiple loading and filtering strategies.
• Preview attachments like PDFs and Videos in the editor.
• Works seamlessly with Action Text, generating the same canonical HTML format it expects for attachments.

Add this line to your application's Gemfile:

gem 'lexxy', '~> 0.1.4.beta' # Need to specify the version since it's a pre-release

And then execute:

bundle install

If you are using propshaft and import maps:

# importmap.rb
pin "lexxy", to: "lexxy.js"
pin "@rails/activestorage", to: "activestorage.esm.js" # to support attachments

Then import it in your JavaScript entry point:

// app/javascript/application.js
import "lexxy"

If you're using jsbundling-rails, esbuild, webpack, or any other JavaScript bundler, you can install the NPM package:

yarn add @37signals/lexxy
yarn add @rails/activestorage # to support attachments

Then import it in your JavaScript entry point:

// app/javascript/application.js
import "@37signals/lexxy"

By default, the gem overrides Action Text form helpers, so that if you use form.rich_text_area, it will render a Lexxy editor instead of the default Trix editor.

You can opt out of this behavior by disabling this option in application.rb:

config.lexxy.override_action_text_defaults = false

If you do this, you can invoke Lexxy explicitly using the same helpers with a lexxy preffix: lexxy_rich_textarea_tag and form.lexxy_rich_text_area.

This path is meant to let you incrementally move to Lexxy, or to use it in specific places while keeping Trix in others.

For the CSS, you can include it with the standard Rails helper:

<%= stylesheet_link_tag "lexxy" %>

Of course, you can copy the CSS to your project and adapt it to your needs.

For applying the same styles to rendered Action Text content, you need to override the current default by adding this template app/views/layouts/action_text/contents/_content.html.erb:

<div class="lexxy-content">
  <%= yield -%>
</div>

To apply syntax highlighting to rendered Action Text content, you need to call the highlightAll function from Lexxy. For example, create a Stimulus controller in app/javascript/controllers/syntax_highlight_controller.js:

import { Controller } from "@hotwired/stimulus"
import { highlightAll } from "lexxy"

export default class extends Controller {
  connect() {
    highlightAll()
  }
}

Then update the Action Text Content template to include the data-controller attribute:

<div data-controller="syntax-highlight" class="lexxy-content">
  <%= yield -%>
</div>

You can add a Lexxy instance using the regular Action Text form helper:

<%= form_with model: @post do |form| %>
  <%= form.rich_text_area :content %>
<% end %>

Under the hood, this will insert a <lexxy-editor> tag, that will be a first-class form control:

<lexxy-editor name="post[body]"...>...</lexxy-editor>

The <lexxy-editor> element supports these options:

• placeholder: Text displayed when the editor is empty.
• toolbar: Pass "false" to disable the toolbar entirely, or pass an element ID to render the toolbar in an external element. By default, the toolbar is bootstrapped and displayed above the editor.
• attachments: Pass "false" to disable attachments completely. By default, attachments are supported, including paste and Drag & Drop support.

Lexxy uses the ElementInternals API to participate in HTML forms as any standard control. This means that you can use standard HTML attributes like name, value, required, disabled, etc.

Prompts let you implement features like @mentions, /commands, or any other trigger-based suggestions. When you select an item from the prompt, you have two options:

1. Insert the item as an Action Text custom attachment. This allows you to use standard Action Text to customize how it renders or processes them on the server side.
2. Insert the item as free text in the editor.

Lexxy also lets you configure how to load the items: inline or remotely, and how to do the filtering (locally or on the server).

The first thing to do is to add a <lexxy-prompt> element to the editor:

<%= form.rich_text_area :body do %>
  <lexxy-prompt trigger="@">
  </lexxy-prompt>
<% end %>

The trigger option determines which key will open the prompt. A prompt can load its items from two sources:

• Inline, by defining the items inside the <lexxy-prompt> element.
• Remotely, by setting a src attribute with an endpoint to load the items.

Regardless of the source, the prompt items are defined using <lexxy-prompt-item> elements. A basic prompt item looks like this:

<lexxy-prompt-item search="...">
  <template type="menu">...</template>
  <template type="editor">
    ...
  </template>
</lexxy-prompt-item>

Where:

• search contains the text to match against when filtering.
• template[type= "menu"] defines how the item appears in the dropdown menu.
• template[type= "editor"] defines how the item appears in the editor when selected.

Imagine you want to implement a mentions feature, where users can type "@" and select a person to mention. You want to save mentions as action text attachments for further server-side processing when the form is submitted.

First, you need to include the ActionText::Attachable concern in your model, and you need to define the #content_type method to return a value like application/vnd.actiontext.<prompt name>, where <prompt name> is the value of the name attribute you will set in the <lexxy-prompt> element later. Let's use mention as the prompt name:

# app/models/person.rb
class Person < ApplicationRecord
  include ActionText::Attachable
  
  def content_type
    "application/vnd.actiontext.mention"
  end
end

By default, the partial to render the attachment will be looked up in app/views/[model plural]/_[model singular].html.erb. You can customize this by implementing #to_attachable_partial_path in the model. Let's go with the default and render a simple view that renders the person's name and initials:

# app/views/people/_person.html.erb
<em><%= person.name %></em> (<strong><%= person.initials %></strong>)

On the editor side, let's start with the inline approach by rendering all the prompt items inside the <lexxy-prompt> element:

<%= form.rich_text_area :body do %>
  <lexxy-prompt trigger="@" name="mention">
    <%= render partial: "people/prompt_item", collection: Person.all, as: :person %>
  </lexxy-prompt>
<% end %>

With app/views/people/_prompt_item.html.erb defining each prompt item:

<lexxy-prompt-item search="<%= "#{person.name} #{person.initials}" %>" sgid="<%= person.attachable_sgid %>">
  <template type="menu"><%= person.name %></template>
  <template type="editor">
    <%= render "people/person", person: person %>
  </template>
</lexxy-prompt-item>

Notice how the template for rendering the editor representation (`type=" editor") uses the same template as the attachment partial. This way, you ensure consistency between how the mention looks in the editor and how it will render when displaying the text in view mode with Action Text.

Two important additional notes to use action text with custom attachments:

• Each <lexxy-prompt-item> must include a sgid attribute with the global id that Action Text will use to find the associated model.
• The <lexxy-prompt> must include a name attribute that will determine the content type of the attachment. For example, for name= "mention", the attachment will be saved as application/vnd.actiontext.mention.

For moderately large sets, you can configure Lexxy to load all the options from a remote endpoint once, and filter them locally as the user types. This is a good balance between performance and responsiveness.

Continuing with the mentions example, we could have a controller action that returns all people as prompt items, and configure it as the remote source via the src attribute:

<lexxy-prompt trigger="@" src="<%= people_path %>" name="mention">
</lexxy-prompt>

We could define the controller action to serve the prompt items like this:

class PeopleController < ApplicationController
  def index
    @people = Person.all

    render layout: false
  end
end

And the action would just list the prompt items:

<% @people.each do |person| %>
  <%= render "people/prompt_item", person: person %>
<% end %>

If you don't want to use custom action text attachments, you can configure prompts to simply insert the prompt item HTML directly in the editor. This is useful for things like hashtags, emojis, or other inline elements that don't require server-side processing.

To enable these, you must add the insert-editable-text attribute to the <lexxy-prompt> element:

<lexxy-prompt trigger="@" src="<%= people_path %>" insert-editable-text>
</lexxy-prompt>

When configured like this,if you select an item from the prompt, the content of the template[type= "editor"] will be inserted directly in the editor as HTML you can edit freely, instead of as an <action-text-attachment> element. Notice that in this case, you need to make sure that the HTML is compatible with the tags that Lexxy supports.

There are scenarios where you want to query the server for filtering, instead of loading all options at once. This is useful for large datasets or complex searches. In this case, you must add the remote-filtering attribute to the <lexxy-prompt> element:

<lexxy-prompt trigger="@" src="<%= people_path %>" name="mention" remote-filtering>
</lexxy-prompt>

By default, the SPACE key will select the current item in the prompt. If you want to allow spaces in the search query, you can add the supports-space-in-searches attribute to the prompt. This can be handy to search by full names in combination with remote filtering.

• trigger: The character that activates the prompt (e.g., "@", "#", "/").
• src: Path or URL to load items remotely.
• name: Identifier for the prompt type (determines attachment content type, e.g., name= "mention" creates application/vnd.actiontext.mention). Mandatory unless using insert-editable-text.
• empty-results: Message shown when no matches found. By default it is "Nothing found".
• remote-filtering: Enable server-side filtering instead of loading all options at once.
• insert-editable-text: Insert prompt item HTML directly as editable text instead of Action Text attachments.
• supports-space-in-searches: Allow spaces in search queries (useful with remote filtering for full name searches).

• search: The text to match against when filtering (can include multiple fields for better search).
• sgid: The signed GlobalID for Action Text attachments (use attachable_sgid helper). Mandatory unless using insert-editable-text.

This is an early beta. Here's what's coming next:

• Configurable editors in Action Text: Choose your editor like you choose your database.
• More editing features:
  • Tables
  • Text highlighting
• Image galleries: The only remaining feature for full Action Text compatibility
• Install task that generates the necessary JS and adds stylesheets.
• Configuration hooks.
• Standalone JS package: to use in non-Rails environments.

To build the JS source when it changes, run:

yarn build -w

To the sandbox app:

bin/rails server

The sandbox app is available at http://localhost:3000. There is also a CRUD example at http://localhost:3000/posts.

• lexxy:initialize: Fired whenever the <lexxy-editor> element is attached to the DOM and is ready for use.
• lexxy:change: Fired whenever the editor content changes.
• lexxy:file-accept: Fired whenever a file is dropped or inserted into the editor. You can access the File object through the file property. Call preventDefault on the event to cancel upload and prevent attaching the file.

• Bug reports and pull requests are welcome on GitHub Issues. Help is especially welcome with those tagged as "Help Wanted".
• For questions and general Lexxy discussion, please use the Discussions section

The gem is available as open source under the terms of the MIT License.