docs: expand information on plugin placement in layout standard

[dopenguin]

Summary

Add additional information on how (custom) plugins may be played in layout: 'standard'.

Instructions for local reproduction and review

Read it.

[github-actions]

PR Preview Action v1.8.0
🚀 View preview at https://Dataport.github.io/polar/pr-preview/pr-555/
Built to branch gh-pages at 2026-04-20 11:19 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[warm-coolguy]

🏓 @dopenguin

https://dataport.github.io/polar/pr-preview/pr-555/docs-html/reference/interfaces/_polar_polar.PluginOptions.html

The rendered docs show that the links do not resolve as intended. This is probably due to the field renderType not being defined in PluginOptions.

It is furthermore confusing that one layouting system is explained as part of parameters and one as part of the type.

Proposed solution: Introductory text explains that there's two layouting systems available and briefly explains their difference. Parameters to PluginOptions further elaborate, and missing renderType is added.

Option: PluginOptions could become some sort or Either type, since either displayComponent/layoutTag are relevant, or renderType is. However, I don't know how to write this ad hoc.

[dopenguin]

🏓 @dopenguin

https://dataport.github.io/polar/pr-preview/pr-555/docs-html/reference/interfaces/_polar_polar.PluginOptions.html

The rendered docs show that the links do not resolve as intended. This is probably due to the field renderType not being defined in PluginOptions.

It is furthermore confusing that one layouting system is explained as part of parameters and one as part of the type.

Proposed solution: Introductory text explains that there's two layouting systems available and briefly explains their difference. Parameters to PluginOptions further elaborate, and missing renderType is added.

Option: PluginOptions could become some sort or Either type, since either displayComponent/layoutTag are relevant, or renderType is. However, I don't know how to write this ad hoc.

I've updated the wording which should be more inline with the actual implementation cfcb605.

However, linking to IconMenuPluginOptions in the rendered documentation does not seem to be working. @oeninghe-dataport any idea?

Also 🏓 to you.