[Feature request] Custom banner types for versioned docs
planned
Andrew Lyons
For projects which have multiple stable versions it would be useful to have a different or custom banner.
For example, we have a master branch for the next version of our project, 1-2 stable versions, and 1-2 versions in security support.
We would like the ability to mark these with relevant banners as the existing criteria do not much.
Jeroen van den Hout
We would like to add a deprecated banner, in addition to the unreleased and unmaintained banners. It would be nice if we could swizzle the list of banner components similar to how we can swizzle
MDXComponents
to add custom components, and allow custom options for the version banner
property (currently unreleased
and unmaintained
are hardcoded).
Joshua Chen
planned
This is already marked as planned in code. We just need enough use-cases and a solid API design that is sufficiently extensible :)
Andrew Lyons
Joshua Chen: Ah great, thanks. I did look for such an issue in both Canny and GH issues but couldn't see anything relevant.
Happy to provide more information on use-case if that's useful.
Marika Marszalkowski
Joshua Chen: Then, I'd like to add my use case:
We have versioned documentation. Once we announce a new version of our product, I would like to add a banner to the current version that points to the announcement. I cannot use the announcement bar, because we also use multiple plugins and I don't want the banner to appear on pages of other plugins.