getcontenttools.com

What it is

ContentTools is a WYSIWYG editor library for HTML content, positioned as a “small but polished” inline page-editing tool. It can be added to any HTML page, allowing users to edit content directly on the page and use the toolbox, bottom inspector bar, and properties dialog to insert, adjust, and modify the underlying HTML.

Core capabilities

In terms of functionality, it covers common content-editing scenarios: editable region indicators, text input and creating new content with Enter, inserting images/videos/tables, converting paragraphs into lists, drag-and-drop ordering of content blocks, resizing images and videos, deleting elements, static non-editable content, and unlimited undo/redo within an editing session. The properties panel supports editing CSS classes, HTML attributes, and inner HTML, making it suitable for CMSs or page editors that need a degree of fine-grained control.

Technology and ecosystem

A key feature of ContentTools is that it is framework-agnostic and does not depend on jQuery, so in theory it can coexist with any JavaScript framework. It consists of multiple libraries, including FSM, HTMLString, ContentSelect, ContentEdit, and ContentTools. These libraries can be used independently or combined into a complete editor. The project is built with CoffeeScript, SASS, and Grunt, which may be friendly for older projects or lower-level customization, but modern frontend teams may need to adapt it to their toolchain.

Pricing and documentation

The main site clearly states that the ContentTools family of libraries is free and open source, hosted, developed, and maintained on GitHub. No commercial edition, paid plan, or official hosted service was found. For documentation, it provides a Getting started guide, full API documentation, examples, and tutorials, covering scenarios such as adding new tools and handling image uploads. Overall, the documentation structure is fairly complete.

Pros, cons, and who it’s for

Its strengths are that it is lightweight, open source, modular, extensible, and not limited to simple rich-text editing. Its drawbacks are that server-side APIs such as image uploads need to be implemented by the user, information on commercial support and maintenance activity is limited, and the build stack feels somewhat traditional. It is suitable for frontend developers, CMS development teams, content platforms, and teams that want to build their own page editor.

Access from China

The main site does not provide information about mainland China access, mirrors, payment methods, or CDN availability, so its China access status can only be marked as unknown. If GitHub access is unstable, domestic teams in China may consider self-hosting the source code and static assets. Alternatives to evaluate include CKEditor, Aloha Editor, or building a lighter editor based on ContentEdit.