add initial minimal plugins docs

[andrewm4894]

• add plugins section to docs
• add getting started page with a quick example
• add a plugin list page to maintain list of popular plugins.

[someone13574]

You probably shouldn't use images where the plugin failed as an example in plugins-quickstart.png and plugins-inspect.png

[andrewm4894]

Yeah not sure if it actually did fail or not. Need understand more what that means.

Maybe we should use the url example as would be better and probably closer to the point of it.

[andrewm4894]

updated images to be better examples

[andreaskoepf]

Dragan's web-retriever will hopefully soon be one of the default plugins that are part of the inference server. When it works correctly we will add it as default option (inactive by default) to the Plugins UI which will make it very simple to activate it.

[andreaskoepf]

see #3277

[andrewm4894]

Yeah - unsure if should just merge this PR and then just do small PR to update the docs again when FE ready?

[andrewm4894]

will update the url to be the OA hosted one for sure as soon as its available

[olliestanley]

I think we should only include OA-provided plugins in this doc, otherwise we will probably end up with many PRs of everyone trying to advertise their own plugins. Web retriever will be merged soon (probably today) so we can edit this and then merge after

[andrewm4894]

Yeah was wondering, although could be nice to just maintain a list of community plugins below the OA ones and then just clearly differentiate between the two and add lots of disclaimers that the community ones are unofficial.

We could only add decent ones then that the community itself has found useful. Would be nice to have them discoverable in some way. Might help encourage bit of an ecosystem around them too.

I could rejig the PR to show sort of what I mean about distinguishing.

[andrewm4894]

Influx does a good job on this with telegraf plugins for example.

https://docs.influxdata.com/telegraf/v1.26/plugins/

Obviously we don't need to overdo any of this either since probably be small enough list to start with.

[andrewm4894]

example of what i mean in latest commit to this pr

[andrewm4894]

i propose we merge this as a starting point and im happy to keep iterating on it (im small fresh pr's) and update as plugins change.

for example once this merged ill need to update corresponding docs etc (e.g. url and info links): #3277

this is fine though as expecting will all be changing a lot - better to have something rather than nothing in the docs and build from there being the thinking.

[github-actions]

❌ pre-commit failed.
Please run pre-commit run --all-files locally and commit the changes.
Find more information in the repository's CONTRIBUTING.md

[github-actions]

❌ pre-commit failed.
Please run pre-commit run --all-files locally and commit the changes.
Find more information in the repository's CONTRIBUTING.md