Relocate core plugin to top of controlpanels plugin list

[twMat]

What the heading says.

The core plugin obviously holds a unique position in TW and is ubiquitus. If it is to be listed at all in the controlpanels plugin list, then it deserves to be emphasized. All other plugins depend on it and some plugins even require a special version of the core plugin so its version number needs to be referenced. I say the core plugin should be permanenty positioned at top of the plugin list. Currently it appears to be "just another plugin":

[pmario]

hmmm. I think, it's the least important plugin in the list. It would be easy to list it as the last one. So if users know, that core is the last plugin in the list it will be easy to find.

IMO normally users need to interact with plugin-settings. The core plugin has no settings tab, it has the ControlPanel

[Jermolene]

Thanks @twMat. The counter argument is that it is helpful for users to understand that the core is just another plugin that they can explore in the usual way. Perhaps there's another way we could mark the special status of $:/core; maybe just a thicker border.

[pmario]

We could add a data-plugin-title="$:/Core" to the plugin-info snippet, if possible. So it would be relatively easy to style some of the plugins differently.

[pmario]

I did a short test

\rules only filteredtranscludeinline transcludeinline macrodef macrocallinline html

a[data-plugin-title="$:/core"] {
  border: 4px solid <<colour primary>>;
}

@Jermolene -- should I create a PR?

[Jermolene]

Thanks @pmario, that's helpful. I think we might need to experiment further to figure out the clearest and most consistent styling. Perhaps we should investigate a special background, as we use for disabled plugins:

The background for disabled plugins is designed to stand out, but we'd want the core plugin to be marked in a subtler way. The core plugin already has a custom icon; perhaps we could just make it a different colour as well (maybe full black?).

[pmario]

Once the data-plugin-title={{!!title}} is assigned, we can do whatever we want with the styling. IMO it's important to add the data-marker so we are able to style it.

[twMat]

@Jermolene

[...] the core is just another plugin that they can explore in the usual way.

Well, it is and it ain't. For one, you must not delete it. But, yes, including it in the plugin list does convey that it is a plugin and it invites for potential exploration which is good.

[...] maybe just a thicker border.

A risk with a border or other visual marker is that it can be mistaken for it somehow being "selected" or "active" in the plugin list, like the switcher lists for Story view or Theme.

I think putting it at top makes most sense. It is a plugin but it is the crown jewel.

[twMat]

@pmario

Once the data-plugin-title={{!!title}} is assigned, we can do whatever we want with the styling. IMO it's important to add the data-marker so we are able to style it.

+1 for this.

Side note: I have temporarily (and less elegantly) solved it like so:

.tc-tab-content:has(>div>p>span>a.tc-plugin-info) div p {
display:flex;
flex-flow:column wrap;
}
.tc-tab-content>div>p>span:has(>a[href="#%24%3A%2Fcore"]) {
order:-1;
}

[pmario]

Moving the core plugin to the top is not really simple. Moving it to the end is simple (I did already test that one). But atm I do not know, how to move it to the front.

[twMat]

@pmario

Moving the core plugin to the top is not really simple. Moving it to the end is simple (I did already test that one). But atm I do not know, how to move it to the front.

Yeah, I know (that is a filter issue in itself!). It is doable like so {{{ 1 2 3 +[reverse[]] 2 +[reverse[]] }}}

[twMat]

@Jermolene

custom icon; perhaps we could just make it a different colour as well (maybe full black?).

That only makes it stand out among other official plugins. In my experience, people have a mix of official and unofficial plugins so the icons can be very arbitrary and eclectic.