Go to file
Peter Savchenko 1a72d2153b
fix(toolbox): shortcuts appearance fixed, icons became optional (#2188)
* fix(toolbox): shortcuts appearing fixed, icons became optional

* rm only from test

* Update tools.spec.ts

* rm useless tests

* Update CHANGELOG.md
2022-11-29 01:57:48 +04:00
.github fix ci (#2182) 2022-11-26 11:32:04 +04:00
.vscode chore(submodules): submodules updated, changelog fixed (#2179) 2022-11-26 00:53:08 +04:00
docs fix(toolbox): shortcuts appearance fixed, icons became optional (#2188) 2022-11-29 01:57:48 +04:00
example chore(submodules): submodules updated, changelog fixed (#2179) 2022-11-26 00:53:08 +04:00
src fix(toolbox): shortcuts appearance fixed, icons became optional (#2188) 2022-11-29 01:57:48 +04:00
test fix(toolbox): shortcuts appearance fixed, icons became optional (#2188) 2022-11-29 01:57:48 +04:00
types fix(toolbox): shortcuts appearance fixed, icons became optional (#2188) 2022-11-29 01:57:48 +04:00
.babelrc [Feature] Block Tunes API (#1596) 2021-04-04 15:10:26 +03:00
.editorconfig Release 2.14 (#799) 2019-06-12 20:38:16 +03:00
.eslintignore Release / 2.18 (#1181) 2020-06-03 11:17:29 +03:00
.eslintrc chore(linting): eslint updated, code linted (#2174) 2022-11-25 21:56:50 +04:00
.gitignore [Feature] Block Tunes API (#1596) 2021-04-04 15:10:26 +03:00
.gitmodules chore(dev): update tools submodules to the last version (#2025) 2022-04-22 18:24:33 +03:00
.npmignore feat(dx): add a dev-server for debugging on mobile devices from a local network (#2009) 2022-04-05 19:49:16 +03:00
.postcssrc.yml Fix hover on the Delete Block button (#659) 2019-03-20 15:46:43 +03:00
.stylelintrc Release 2.0-beta (#387) 2018-08-05 14:51:58 +03:00
CODEOWNERS fix(#2036): scrolling issue with block hovering (#2042) 2022-05-01 15:09:16 +03:00
LICENSE Release 2.16 (#966) 2019-11-30 23:42:39 +03:00
README.md Roadmap updated 2022-06-22 19:48:15 +03:00
cypress.json [Feature] Block Tunes API (#1596) 2021-04-04 15:10:26 +03:00
devserver.js feat(dx): add a dev-server for debugging on mobile devices from a local network (#2009) 2022-04-05 19:49:16 +03:00
package.json bump: 2.26.0-rc.7 2022-11-28 20:28:41 +04:00
tsconfig.build.json Add build tsconfig for automatic deployments (#1784) 2021-09-17 15:47:29 +03:00
tsconfig.json Block tunes as a popover (#2091) 2022-11-03 20:52:33 +03:00
tslint.json Basic initialisation test for Editor.js (#1410) 2020-11-21 21:01:31 +03:00
webpack.config.js feat(icons): codex icons package is used instead of svg sprite (#2173) 2022-11-25 22:26:23 +04:00
yarn.lock build(deps): bump moment from 2.29.2 to 2.29.4 (#2104) 2022-11-26 10:42:23 +04:00

README.md

Backers on Open Collective Sponsors on Open Collective Join the chat at https://gitter.im/codex-team/editor.js

IE / Edge Edge 12+ Firefox Firefox 18+ Chrome Chrome 49+ Safari Safari 10+ iOS Safari iOS Safari 10+ Opera Opera 36+

Roadmap

  • Collaborative editing

    • Implement Inline Tools JSON format In progress #1801
    • Implement Operations creation and transformations
    • Implement Tools API changes
    • Implement Server and communication
    • Update basic tools to fit the new API
  • Unified Toolbox

    • Block Tunes moved left #1815
    • Toolbox become vertical #2014
    • Ability to display several Toolbox buttons by the single Tool #2050
    • Conversion Toolbar uses Unified Toolbox In progress
    • Block Tunes become vertical
    • Conversion Toolbar added to the Block Tunes
  • Ecosystem improvements

image

If you like a project 💗💗💗

If you like Editor.js you can support project improvements and development of new features with a donation to our collective.

👉 https://opencollective.com/editorjs

Sponsors

Support us by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

Backers

Thank you to all our backers! 🙏 [Become a backer]

Contributors

This project exists thanks to all the people who contribute.

We really welcome new contributors. If you want to make some code with us, please take a look at the Good First Tasks. You can write to us on team@codex.so or via special Telegram chat, or any other way.

Documentation

Please visit https://editorjs.io/ to view all documentation articles.

You can join a Gitter-channel or Telegram-chat and ask a question.

Changelog

See the whole Changelog

If you want to follow Editor.js updates, subscribe to our Newsletter.

How to use Editor.js

Basics

Editor.js is a Block-Styled editor. Blocks are structural units, of which the Entry is composed. For example, Paragraph, Heading, Image, Video, List are Blocks. Each Block is represented by Plugin. We have many ready-to-use Plugins and a simple API for creating new ones.

How to use the Editor after Installation.

  • Create new Blocks by pressing Enter or clicking the Plus Button
  • Press TAB or click on the Plus Button to view the Toolbox
  • Press TAB again to leaf Toolbox and select a Block you need. Then press Enter.

  • Select a text fragment and apply a style or insert a link from the Inline Toolbar

  • Use the «three-dots» button on the right to open Block Settings. From here, you can move and delete a Block or apply a Tool's settings, if it provided. For example, you can set a Heading level or List style.

Shortcuts

A few shortcuts are preset as available.

Shortcut Action Restrictions
TAB Show/leaf a Toolbox. On empty block
SHIFT+TAB Leaf back a Toolbox. While Toolbox is opened
ENTER Create a Block While Toolbox is opened and some Tool is selected
CMD+B Bold style On selection
CMD+I Italic style On selection
CMD+K Insert a link On selection

Each Tool can also have its own shortcuts. These are specified in the configuration of the Tool, for example:

var editor = new EditorJS({
  //...
  tools: {
    header: {
      class: Header,
      shortcut: 'CMD+SHIFT+H'
    },
    list: {
      class: List,
      shortcut: 'CMD+SHIFT+L'
    }
  }
  //...
 });

Installation Guide

There are few steps to run Editor.js on your site.

  1. Load Editor's core
  2. Load Tools
  3. Initialize Editor's instance

Step 1. Load Editor's core

Get Editor.js itself. It is a minified script with Editor's core and some default must-have tools.

Choose the most usable method of getting Editor for you.

  • Node package
  • Source from CDN
Option A. NPM install

Install the package via NPM or Yarn

npm i @editorjs/editorjs

Include module in your application

import EditorJS from '@editorjs/editorjs';
Option B. Use a CDN

You can load EditorJS directly from from jsDelivr CDN.

https://cdn.jsdelivr.net/npm/@editorjs/editorjs@latest

For example, place this in your HTML:

<script src="https://cdn.jsdelivr.net/npm/@editorjs/editorjs@latest"></script>

Or download the bundle file and use it from your server.

<script src="editor.js"></script>

Step 2. Load the Tools that you want to make available

Each Block is represented by a Tool. Tools are simple external scripts with their own logic. For example, there is a Header Tool into which you type your heading text. If you want to be able to use this, install the Header Tool the same way as the Editor (Node.js, CDN, local file).

Example: use Header from CDN

<script src="https://cdn.jsdelivr.net/npm/codex.editor.header@2.0.4/dist/bundle.js"></script>

Check Editor.js's community to see more ready-to-use Tools.

Step 3. Create Editor instance

Create an instance of Editor.js and pass Configuration Object with holderId and tools list.

<div id="editorjs"></div>

You can create a simple Editor with only default Paragraph Tool by passing a string with element's Id (wrapper for Editor) as a configuration param. Or use the default editorjs id for wrapper.

var editor = new EditorJS(); /** Zero-configuration */

// equals

var editor = new EditorJS('editorjs');

Or pass a whole settings object.

var editor = new EditorJS({
    /**
     * Create a holder for the Editor and pass its ID
     */
    holder : 'editorjs',

    /**
     * Available Tools list.
     * Pass Tool's class or Settings object for each Tool you want to use
     */
    tools: {
        header: {
          class: Header,
          inlineToolbar : true
        },
        // ...
    },

    /**
     * Previously saved data that should be rendered
     */
    data: {}
});

Saving Data

Call editor.save() and handle returned Promise with saved data.

editor.save()
  .then((savedData) => {
    console.log(savedData);
  });

Example

Take a look at the example.html to view more detailed examples.

Credits and references

About CodeX

CodeX is a team of digital specialists around the world interested in building high-quality open source products on a global market. We are open for young people who want to constantly improve their skills and grow professionally with experiments in cutting-edge technologies.

🌐 Join 👋 Twitter Instagram
codex.so codex.so/join @codex_team @codex_team