Write a guide for plugin developers

[kdmccormick]

Context

Over here @regisb suggested making a step-by-step guide for new plugin developers.

Before doing this, we'll want to settle on a V1 plugin interface.

Acceptance

Write a plugin developer guide containing:

• Introduction ("what is a plugin? why would I make one?")
• Document anatomy of a plugin #33
• https://github.com/overhangio/2u-tutor-adoption/issues/29
• Tutorial of how to make a YAML plugin, by example
• Tutorial of how to make a Python plugin, by example
• https://github.com/overhangio/2u-tutor-adoption/issues/5
• A link to: Provide a publicly-editable list of Tutor plugins #46
• ...Anything else?

This guide will (replace? extend? complement?) the existing plugin development section in the docs.

[kdmccormick]

@regisb What do you think?

[regisb]

I think that the bullet list is pretty comprehensive. I expect that there will not be a single plugin developer guide, but rather a series of tutorials which will be included in a new, dedicated "Plugin development" section of the tutorial docs.

[kdmccormick]

Closing this issue in favor of an identical epic on the platform-roadmap: openedx/platform-roadmap#123