There are few steps to run Editor.js on your site.
Firstly you need to get Editor.js itself. It is a minified script with minimal available
Choose the most usable method of getting an Editor for you.
- Node package
- Source from CDN
- Local file from a project
Install the package via NPM or Yarn
npm i @editorjs/editorjs
Include module at your application
import EditorJS from '@editorjs/editorjs';
You can load specific version of package from jsDelivr CDN.
https://cdn.jsdelivr.net/npm/@editorjs/[email protected]
Then require this script.
<script src="..."></script>
Copy editor.js file to your project and load it.
<script src="editor.js"></script>
Each Block at the Editor.js represented by Tools. There are simple external scripts with their own logic. You'll probably want to use several Block Tools that should be connected.
For example, check out our Header Tool that represents heading blocks.
You can install the Header Tool via the same ways as an Editor (Node.js, CDN, local file).
Check Editor.js's community to see Tools examples.
Example: use Header from CDN
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/bundle.js"></script>
Create an instance of Editor.js and pass Configuration Object.
At least the holderId
option is required.
<div id="editorjs"></div>
You can create a simple Editor only with a default Paragraph Tool by passing a string with element's Id (wrapper for Editor) as a configuration param or use default editorjs
.
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
*/
holderId : '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: {}
});
Editor.js needs a bit of time to initialize. It is an asynchronous action so it won't block execution of your main script.
If you need to know when the editor instance is ready you can use one of the following ways:
It must be a function:
var editor = new EditorJS({
// Other configuration properties
/**
* onReady callback
*/
onReady: () => {console.log('Editor.js is ready to work!')}
});
After you create a new EditorJS
object it will contain isReady
property.
It is a Promise object that resolves when the editor will be ready to work and rejected otherwise.
If there is an error during initialization isReady
promise will be rejected with an error message.
var editor = new EditorJS();
editor.isReady
.then(() => {
/** Do anything you need after editor initialization */
})
.catch((reason) => {
console.log(`Editor.js initialization failed because of ${reason}`)
});
You can use async/await
to keep your code looking synchronous:
var editor = new EditorJS();
try {
await editor.isReady;
/** Do anything you need after editor initialization */
} catch (reason) {
console.log(`Editor.js initialization failed because of ${reason}`)
}
Call editor.saver.save()
and handle returned Promise with saved data.
editor.saver.save()
.then((savedData) => {
console.log(savedData);
});
Also, Editor.js provides useful methods to work with Editor's state.
var editor = new EditorJS({
// Other configuration properties
/**
* onReady callback
*/
onReady: () => {console.log('Editor.js is ready to work!')},
/**
* onChange callback
* Accepts CustomEvent describing what happened
*/
onChange: (editorAPI, event) => {console.log('Now I know that Editor\'s content changed!')}
});
Take a look at the example.html to view more detailed examples.