Fedwiki Plugin Development

Here we gather and describe the sorts of Plugins we would like to see as part of the Federation.

Our aim is to foster a community of developers that build and share expertise in NodeJS, Javascript, and Fedwiki Plugin Development.

We want to be able to drag and drop a page flag onto a Transporter, in order to indicate that we want the transporter to act on that particular page.

We'll take notes as we make a new plugin. We've made a few so this represents the best approach so far.

Here are a couple very early stage I ideas for two Fedwiki plug-ins.

A ProTip Fedwiki Plugin would take the features of the ProTip Chrome Extension, and provide them as a Fedwiki Plugin.

The Factory Plugin renders as brief instructions and a short menu of types, a subset of plugin types available on the origin server, that will transform the plugin when clicked.

Plugins contain documentation pages that describe capabilities, explain specialized markup, and include examples of usefully configured examples.

Plugins often respond to events sent by other plugins as well as wiki-client core modules. This makes another namespace that must be managed. Here we keep an index.

We'll take notes as we make a new plugin. We've made a few so this represents the best approach so far.

The Method plugin has already grown complex interacting across pages and between other plugins. Here I consider how I approached a large increment in functionality when I added units and expressions.

Anyone who programs can make new plugins. We expect community minded organizations to create and publish plugins as open source. Here is how to find these folks.

The Farm Plugin would give access to creating new wikis, claiming them and providing a quick overview of sites in a farm.