There is also the Kirigami AboutItem/AboutPage, but that seems overkill to me:

Inside plasma desktop there's a copy of this Component reading from KPluginMetadata which has a bit less info (no libraries) and different property names. It's the "About" page in applet config windows.

Maybe it might be worth it to reupstream it either as separate thing with a different design or make the AboutItem/Page dynamic https://invent.kde.org/plasma/plasma-desktop/-/blob/41fd502350a9e3657753e528854ca77e8d4f6d56/desktoppackage/contents/configuration/AboutPlugin.qml

Inside plasma desktop there's a copy of this Component reading from KPluginMetadata which has a bit less info

Thanks, this is a good example which fits the usecase very well.

Maybe it might be worth it to reupstream it either as separate thing with a different design or make the AboutItem/Page dynamic

If we decide to use this, I will look into it.

@davidre What is your opinion regarding the presentation of the info. With the component you linked, an info-button might make the most sense. (IMHO too much info to put it inline).

Yeah let's go with an info button for now.

Instead of it opening a window maybe we could try pushing it as a new page? (if we can rely on having a pagestack)

Personally, I would prefer a window. Another argument for this is that for the config we need a window anyways. Meaning it would be consistent.

What would the advantage of a new page be? I do not consider clicking the info button going to a new component (like the SDDM KCM behavior button), just popping in some extra info

https://invent.kde.org/frameworks/kcmutils/-/merge_requests/84 landed and is used n two Plasma KCMS, the next step is de-duplicating the about plugin stuff