Added Plugins section with curently compatible plugins

[jeremymeyers]

I made a table with all the plugins listed as compatible on #170 ... the plugin names would need to be verified in terms of being able to use them to install correctly but since there doesn't seem to be anywhere else in the docs that this lives i thought it might be a good addition.

[JohnTheGr8]

Quick thoughts:

1. listing plugins that have not been ported to this project in its Readme will probably confuse people, especially with the text Here are some actively maintained plugins you can install.
2. the first two columns can be merged into one to make this less noisy (visually)
3. in my opinion the last column can be omitted

[jeremymeyers]

@JohnTheGr8 the "not ported" denotes plugins that were created for Wox that run in Flow without needing to make any changes. The language could be clearer.

[jjw24]

@jeremymeyers I think it would be better to reference this table in our documentation site instead.

What do you guys think if we:

• move Usage section above Integrations
• include it in Integrations section as another bullet point instead.
• A simple one liner for the bullet point along the lines of: Flow has also integrated plugins from other launchers, visit here for a list of plugins you can use from them
• Move your Plugins section contents to the docs site: https://github.com/Flow-Launcher/docs as a brand new page called Migrated Plugins (or whatever heading you see fit)

The reason for this is because I would think it's better to keep the readme light and concise, only the necessary information for new users that is needed to get going. Advanced users as well as launcher users can dig into the doco site to find out more what Flow offers additionally.

Let me know what you guys think.

[jeremymeyers]

works for me, i just kinda wanted to get it started

[jjw24]

You can make the changes to the same pr here, and let me know when you have PRed the docs repo

[jeremymeyers]

New doc repo is here Flow-Launcher/docs#6 ... will make changes to readme.md in a sec

[jjw24]

instead of a separate section, could this be just a bullet point in Integrations section please

[jeremymeyers]

it can though i made it a separate thing because I'm not sure an average user would think to look for plugin installation information under an "integrations" section and the extensibility is a core Flow feature. (my focus generally is documentation UX). But happy to do whatever.

[jjw24]

Good point. Let's keep this section then, once the python auto install feature is rolled out I might merge Integration into the Plugin section as well so we can just use it as a quick guide on using plugins and where to find more info