Creating Factor Plugins

Project Setup

Factor plugins are standard Node modules that "hook" into Factor functionality.

The first step in creating a plugin is to create a folder that includes a package.json file.

To make your project a Factor plugin all that is needed is to add the factor property.

If you'd like your plugin to be "auto-loaded" in your user's applications, you'll also need to set the load property and assign the entry files.

// package.json
  "name": "excellent-factor-plugin",
  "factor": {
    "load": {
      "app": "index", // Loads index.js in webpack app
      "server": "server" // Loads server.js in server environment

Development Setup

To work on your plugin and see what it does, you'll need to add it to a Factor application or theme. If you have an app setup locally for development, then you'll need to reference the local plugin in its dependencies.

To do this, we recommend looking into:

Starting Your Plugin

The first step is to add some code to your plugin "entry" or "main" files (set with load property).

These files typically "hook" into Factor via functions, filters and callbacks. A few examples of what you can do:

Index.js and Server.js

There are two environments in Factor, the Webpack "app" and the Express "server".

With the entry files, you'll typically want to split code that is meant to run in the client into index.js and code that is meant for the server into server.js.

However the naming and loading of these files can be completely controlled using the package.json > load property.

Allowing Customization

To make your plugin customizable, use filters, callbacks and events as well as adding editable settings to factor-settings and employing CSS variables that can be set from apps.

Settings and Styles


Anything that should be editable belongs in a factor-settings.js file in your plugin. As an example, adding settings to this file like this:

export default {
  myWelcomePlugin: {
    bannerText: "Welcome",
    route: "/welcome"

Means that users can easily override these settings with their own factor-settings.js file.


If your plugin has components that include their own style, use CSS variables and a factor-styles.less file to set defaults.

  <div class="banner"></div>
  import { setting } from "@factor/api"
  export default {
    methods: { setting }
<style lang="less">
  .banner {
    background: var(--welcome-banner-bg);

and in your CSS/LESS file:

.factor-app {
  --welcome-banner-bg: #0471ff;

This approach makes your plugin completely customizable and allows you to set ideal defaults for a great initial experience.

Filters, Callbacks and Events

Use filters, callbacks and events to maximize the amount of code in your plugin that can be customized.

Learn more about filters, callbacks, and events →

Standards and Conventions

Once you've created your plugin, you likely want to set it up for distribution. Here are standards for assets and plugin quality that will help your plugin get discovered and used.


Add a plugin icon in .svg format sized at 200px x 200px called icon.svg and place it in the root of your plugin.


Add screenshots to the root of your plugin. These will be used in plugin listings.

Add a primary screenshot sized at 1080px x 720px called screenshot.jpg or screenshot-wide.jpg.

Add a tall screenshot at 720px x 1080px called screenshot-tall.jpg.

Other screenshots are allowed and are used in galleries for your app. Additional screenshots should start with screenshot- or screenshot-tall- and will be sorted alphanumerically.

Plugin Name Spacing

The name of your extension should generally include the word factor-. This way it will be clear it's a Factor plugin and it will also help with SEO.

Apply your plugin name as a "name space" when naming fields and filters in order to avoid naming collisions with other authors and developers.

  • Don't name your filter/field/id: comments or job
  • Do prefix your filters/fields/id with a namespace or similar: my-plugin-comments, myPluginId

Documenting Your Plugin

Never assume people know how to use your plugin, we recommend adding the following instructions to your

  • Overview including Purpose and/or motivation behind the plugin
  • Installation
  • Options and Settings
  • Utilities available (factor setup)
  • FAQ or Related documentation and context links


Factor plugins should be compatible with the GPLv2 license.

Distribution and Discovery

After you've published your plugin as an NPM package, write us an email at [email protected] about getting your plugin listed on the Factor plugins listing →