Latest
Introduction
User Guide
Admin Guide
Developer guide
API Reference
Plugin overview
There are numerous ways you can add functionality to the . This guide will give you an understanding of what a plugin is and the basic structure of a plugin.
Most of what you can see in the are plugins. Even text styles are small plugins. In the image below you can see a basic overview of the different parts of the UI and where plugins can be added.
Anatomy of a simple sidebar plugin
For a more practical step by step instructions on how to get started using the skeleton DevKit plugin see the quickstart guide.
The skeleton plugin will add a plugin to the sidebar with a few simple UI components. If you look at our Devkit skeleton plugin you will find the main plugin source in the
src directory.1
src/
2
scss/
3
index.scss
4
index.js
5
DevKitPackage.js
6
DevKitComponent.js
Copied!
index.js
The index.js file is the starting point. When loaded this file will call
registerPlugin() in the which register the plugin package.1
import {DevkitPackage} from './DevKitPackage'
2
import {registerPlugin} from 'writer'
3
​
4
(() => {
5
// Register the plugin with the Writer when registerPlugin() is available
6
if (registerPlugin) {
7
registerPlugin(DevkitPackage)
8
}
9
else {
10
console.error('Register method not yet available')
11
}
12
})()
Copied!
DevKitPackage.js
The package defines a
configure() function. This function is called by the after the plugin has been loaded and registered successfully. As parameters you get a config object which has all the methods you need to register components, commands, tools, keyboard shortcuts, translation labels and what not. In essences, the config object is what allows you to define all the bits and pieces of your plugin and define where they should go in the .The DevKit skeleton package imports a sass/css file and a its own UI component, the
DevKitComponent, which is added to the sidebar using config.addToSidebar(). It also registers a translation label using config.addLabel().1
import './scss/index.scss'
2
import {DevKitComponent} from './DevKitComponent'
3
​
4
const DevKitPackage = {
5
name: 'npwriterdevkit',
6
id: 'se.infomaker.npwriterdevkit',
7
configure: function(configurator, pluginConfig) {
8
​
9
configurator.addToSidebar('main', pluginConfig, DevKitComponent)
10
​
11
configurator.addLabel('Devkit plugin loaded', {
12
en: 'Devkit plugin loaded',
13
sv: 'Devkit plugin inläst'
14
})
15
}
16
}
17
​
18
export {DevKitPackage}
Copied!
DevKitComponent.js
User interface components are built using the React like Substance components. You will see this again and again in both tools, content objects, popovers and all other UI components you will define. The provides a few basic UI components and an API to manipulate most aspects of the and article data.
The DevKit skeleton plugin imports a
Component from the substance module which all UI components inherit from. It also imports a UIButton and the api from the writer module.The most important method is the
render() method. See the DevKit skeleton for the complete source.1
import {Component} from 'substance'
2
import {UIButton, api} from 'writer'
3
​
4
class DevKitComponent extends Component {
5
render($) {
6
const el = $('div').addClass('devkit')
7
​
8
const button = $(UIButton, {
9
label: 'Click me'
10
})
11
.on('click', () => {
12
this.increaseClickCount()
13
})
14
​
15
el.append([
16
$('h2').append(
17
this.getLabel('Devkit plugin loaded')
18
),
19
$('p').append(
20
`You have clicked ${this.state.clickCount} times`
21
),
22
button
23
])
24
​
25
return el
26
}
27
​
28
increaseClickCount() {
29
// ...
30
}
31
​
32
export {DevKitComponent}
33
}
Copied!
Last modified 1yr ago