Tracking issue for plugin docs update

[willingc]

Let's focus a bit on updating plugin docs. This issue contains links to other plugin related documentation requests.

Issues

• add to troubleshooting: plugin issues due dropping pydantic 1 support #567
  Update plugin documentation to fully use pyproject.toml #492 - Largely a duplicate of Update first-plugin example to best practices #440
  Update first-plugin example to best practices #440 - Just do the task
  Add 'Plugin manager' section to 'napari architecture guide' #321 - Add npe2 architecture overview
  Plugin anatomy, or what is a plugin? #225 - New doc: architecture/structure/anatomy of a plugin
  User focused plugin contributions page #224 - Add wording from Edit plugin landing page to add links and update information #581 to Start Using Plugins landing page intro. Close with Edit user plugin installation page to simplify instructions #586
  Update plugin homepage to highlight the relationship of plugins to core napari #223 - See note below
  Reorganising and improving plugin documentation #153 - Suggestions and user personas
  Add documentation of make_napari_viewer and DynamicPlugin #150 - More related to testing.
  Clarify Plugin Best Practices regarding depending on napari[all] #131 - Check if in docs content. if not, use content here
  Documenting file formats supported by napari ecosystem #44 - Document file format support in napari core; note community plugins that extend support
  Detailed guide for adding menu contributions #585 - Document usage of menu contributions from NAP-6
  Inconsistencies between plugin docs and cookiecutter #355 - Should close

PRs in other repos

napari/napari-plugin-engine#61 - deprecation info for napari-plugin-engine and migration links to npe2

Rough plan

• update plugin landing page Edit plugin landing page to add links and update information #581
• read and edit existing user pages for installing, discovering, using plugins Edit plugin landing page to add links and update information #581 Edit user plugin installation page to simplify instructions #586
• read and edit existing developer pages for creating, testing, troubleshooting, migrating from 1 to npe2
• Review and/or add napari plugin engine, npe2, architecture section, menu contributions
• Review or create file format page (core and community plugin)
• Noodle over a way to highlight community maintained plugins to build awareness and discovery

[willingc]

From #223, potentially add:

Plugins are a powerful way to extend the functionality of napari and share these extensions with the community. Plugins facilitate the integration of domain-specific features into napari, while preserving napari as a versatile and domain-agnostic viewer at its core. Existing plugins address a diverse array of challenges, including image segmentation, support for new file formats during reading and writing, single-cell tracking, and animation creation within napari. While scripts and widgets can also be used to extend napari, plugins offer the most convenient method for publicly sharing additional features.

Check out the user focused content to guide you through installing and using napari plugins, or the developer focused content to start creating your own plugins for napari.

Also easily redistributable since a python package.

[willingc]

@DragaDoncila @psobolewskiPhD @melissawm Plugin ❤️