Skip to main content

django-rmeditor

A lightweight, self-hosted rich text editor for Django. It outputs plain HTML, so it is a drop-in replacement for a TextField / tinymce HTMLField with no data migration. No CDN, no API key, no branding, no word/usage limits.

  • Pure vanilla JS (no jQuery, no build step).
  • Auto-enhances any <textarea class="rmeditor">.
  • Existing content is loaded as-is (HTML in / HTML out).
  • Configurable toolbar per field.
  • Paste cleaning (strips Word/Office junk) + basic XSS sanitize.
  • Works with Django forms, the admin, or hand-written templates.

Install

pip install django-rmeditor
# settings.py
INSTALLED_APPS = [
    ...,
    "rmeditor",
]

Make sure django.contrib.staticfiles is set up (it is by default) and run collectstatic in production.

Usage

1. Hand-written templates (no form/widget)

{% load rmeditor %}
{% rmeditor_media %}   {# include once per page, e.g. in your base template #}

<form method="post">
  {% csrf_token %}
  <textarea name="body" class="rmeditor"
            data-tools="format fontsize | bold italic underline | bullist numlist | link image | removeformat">
    {{ object.body }}
  </textarea>
  <button type="submit">Save</button>
</form>

The textarea stays in the form (hidden) and always holds the current HTML, so your existing view code that reads request.POST["body"] keeps working unchanged.

Autochange — enhance every textarea (no class needed)

To convert all textareas on a page into editors without touching each one (like tinymce's selector:'textarea'), enable autochange:

{% load rmeditor %}
{% rmeditor_media auto="textarea" %}   {# every <textarea> becomes an editor #}

or from JS:

<script src="/static/rmeditor/js/rmeditor.js"></script>
<script>RMEditor.auto("textarea");</script>   <!-- or any CSS selector -->

or globally before the script loads:

<script>window.RMEDITOR_AUTO = "textarea.rich";</script>

Opt a textarea out of autochange with class="no-rmeditor" or data-rmeditor="off". This makes replacing tinymce a one-line change: swap the tinymce script/init for {% rmeditor_media auto="textarea" %}.

2. Model field

from django.db import models
from rmeditor.fields import RichTextField

class Article(models.Model):
    body = RichTextField(blank=True, default="")

RichTextField is a TextField subclass — same column, no data difference. Switching an existing TextField/HTMLField to it needs only a no-op migration.

3. Form widget

from django import forms
from rmeditor.widgets import RichTextWidget

class ArticleForm(forms.ModelForm):
    class Meta:
        model = Article
        fields = ["body"]
        widgets = {"body": RichTextWidget(tools="bold italic link")}

Toolbar tokens

format (paragraph/H1/H2/H3 dropdown), fontsize (px-based dropdown), bold, italic, underline, strike, forecolor, bullist, numlist, indent, outdent, alignleft, aligncenter, alignright, justify, link, unlink, image, table, rowadd, rowdel, coladd, coldel, removeformat, source (view HTML), undo, redo.

Table tokens: table inserts a table (prompts for rows,columns); rowadd/rowdel add/delete a row and coladd/coldel add/delete a column relative to the cell the caret is in. Use | for a separator. Set per field with data-tools="..." or on the widget with RichTextWidget(tools="...").

JavaScript API

RMEditor.get(el)            // instance for a textarea node or its id ("" if none)
RMEditor.getHTML(el)        // current HTML
RMEditor.setHTML(el, html)  // replace content
RMEditor.getText(el)        // plain text, trimmed
RMEditor.syncAll()          // flush every editor into its textarea

el may be the textarea DOM node or its id string.

Migrating from tinymce

  • Replace the tinymce script/tinymce.init(...) with {% rmeditor_media %} and add class="rmeditor" to the textareas.
  • tinymce.get("x").setContent(html) → RMEditor.setHTML("x", html)
  • tinymce.get("x").getContent({format:"text"}) → RMEditor.getText("x")

Storage stays HTML, so rendered pages ({{ field|safe }}), PDFs, and API/mobile consumers are unaffected.

Notes / limits (v0.1)

  • Uses document.execCommand (deprecated but supported in all current browsers).
  • Tables support insert plus add/remove row and column. Cell merging/splitting and media (video/embed) editing are out of scope; existing such content is preserved and still renders.
  • Client-side sanitize is a basic guard. For untrusted authors, also sanitize on the server (e.g. bleach) before rendering with |safe.

License

MIT

Release files for django-rmeditor 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-rmeditor 0.1.6
File Size Uploaded
django_rmeditor-0.1.6.tar.gz 17.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for django-rmeditor 0.1.6
File Interpreter ABI Platform
django_rmeditor-0.1.6-py3-none-any.whl Python 3 none any Details

Total release size: 34.5 kB

Release files / django_rmeditor-0.1.6.tar.gz

Download URL django_rmeditor-0.1.6.tar.gz
Size 17.2 kB
Tags Source
SHA-256 checksum
How to use checksums
39c8f790d57615b090d25e67b6207d5a8935998186787b5b89f03a0574d12df4
BLAKE2b-256 checksum
How to use checksums
ee3701d873f5f3e7b43131fc3d5dc8571da43aa6ce88d6e0c8f2b71aaa9b7879
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 25, 2026.

Transparency log

Release files / django_rmeditor-0.1.6-py3-none-any.whl

Download URL django_rmeditor-0.1.6-py3-none-any.whl
Size 17.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0eebb0cf21555b02453dc0c5d98dab6e0ee7ef828db26fcb4f328689f2c72a66
BLAKE2b-256 checksum
How to use checksums
9fc9f812e394872c00ede801c83402f7c68001658cce32ac91243fc4221dba0e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 25, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.15

2 release files

0.1.14

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

This release

0.1.6 This release

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page