We need a good way to manage updates to a server with independent plugins installed.

￭ Created a public script which installs the custom plugins. Remember to run this script each time wiki is installed. There is an example. github

￭ Report plugins available on any server. Include factory summary or synopsis. Possibly categorize these as conventional or exceptional. See Plugins Installed Here

￭ Too hard: Install a new custom plugin with npm --save followed by a commit and push to a private clone of wiki-node. Merge changes from the upstream in git and then publish this to a public scoped npm module and installing it with npm on all managed servers. npm issue

# Categories

We will categorize plugins based on where they are found and what they can do.

￭ Core plugins are required by core javascript and are included within client.js.

￭ Standard plugins are well known by name and expected to be present in all servers.

￭ Data plugins retrieve, process, provide or display information for use by other items.

￭ Work plugins (new) are those addressing a specific kind of work and recognized by their number on a server.

￭ Other plugins declare some category not already included in this breakdown.

The Factory can usefully grow vertically to allow maybe twice as many choices per column. Beyond this, and because some plugins don't interact with the Factory well, a final option, "more", will open an Available Plugins page.

Another alternative would be to design some sort of favorite scheme for obscure plugins of interest to an individual user. The persistence issue alone makes this unattractive. See Managing the Factory Menu

Another alternative would be to just keep a script handly to install all the custom plugins and run that again every time wiki is reinstalled.