@educandu/educandu-plugin-example

educandu-plugin-example

An example plugin for educandu

Prerequisites

• node.js ^20.0.0
• optional: globally installed gulp: npm i -g gulp-cli

The output of this repository is an npm package (@educandu/educandu-plugin-example).

Development

• Clone this repository
• Adjust the names so that they suit your purpose (see also the naming conventions below)
• Adjust the CI/CD scripts so you can publish automtically (or remove them for manual publishing)

Usage

Import the published package into your educandu driven website:

$ yarn add @educandu/educandu-plugin-example

Add the plugin info to the application's custom resolvers module:

import ExamplePlugin from '@educandu/educandu-plugin-example';

export default {
  resolveCustomPageTemplate: null,
  resolveCustomHomePageTemplate: null,
  resolveCustomSiteLogo: null,
  resolveCustomPluginInfos: () => [ExamplePlugin]
};

Add the plugin name, the translations and any additional controllers to your server config:

import educandu from '@educandu/educandu';
import { createRequire } from 'node:module';
import ExampleController from '@educandu/educandu-plugin-example/example-controller.js';

const require = createRequire(import.meta.url);
const examplePluginTranslationsPath = require.resolve('@educandu/educandu-plugin-example/translations.json');

educandu({
  plugins: [/* your other plugins here */, 'educandu/educandu-plugin-example'],
  resources: [/* your other translations here */, examplePluginTranslationsPath],
  additionalControllers: [/* your other additional controllers here */, ExampleController],
  /* your other server config here */
});

Import the plugin styles to your main LESS entry point:

// Base styles from Educandu:
@import url('@educandu/educandu/styles/main.less');

// Styles for the custom plugin:
@import url('@educandu/educandu-plugin-example/example.less');

// Other styles here

Of course, if your plugin does not require any additional controller, or if it doesn't add any styles or translations, the above steps can be skipped accordingly. The bare minimum configuration is to add the plugin info module to the custom resolvers and the plugin type name into the list of activated plugins in the server configuration.

Naming conventions

You need to come up with two good names:

• A namespace that is unique to your person or organization.
  • In best case this is also your Github/NPM organization name.
  • If you don't have an organization, use a non-common suitable name as namespace.
• A plugin name that clearly describes the purpose of your plugin.

In the case of this repository, the namespace is educandu (as this is also the Github/NPM namespace used) and the plugin name is (obviously): example.

Out of these two parts you can generate according to these templates:

• Template {namespace}/educandu-plugin-{plugin-name} (all kebab-cased), example: educandu/educandu-plugin-example
  • use this for the Github repository name and the NPM package name
  • use this also as the typeName for the plugin in the info.js module
  • use this also as the namespace for the plugin translations in the *.yml files
• Template EP_{Namespace}_{PluginName}_{PutYourCssClassNameHere} (all Pascal-cased), example: EP_Educandu_Example_MyClassName
  • use this for CSS classes that are added by the plugin

For example, if a person called "John Doe" wants to publish a plugin called "Slide show", the names could be:

• john-doe/educandu-plugin-slide-show
• EP_JohnDoe_SlideShow_HeaderImage

OER learning platform for music

Funded by 'Stiftung Innovation in der Hochschullehre'

A Project of the 'Hochschule für Musik und Theater München' (University for Music and Performing Arts)

Project owner: Hochschule für Musik und Theater München
Project management: Ulrich Kaiser