config_order for base element

[RisingSunLight42]

To explain my problem, here what I would like to do :

I would like to put in a specific order different plugin, and first base.header.
But, after that, I want to place the other attributes from base, so base.activity, etc.
When I do that, the element is ordered at the bottom, like when we do not specify the placement 😢

❓ Can we place specifically the other attributes like base.activity or base.community ?

[lowlighter]

Excluding the introduction, these are the handle for the base sections plugin ordering:

metrics/source/templates/classic/partials/_.json

Lines 2 to 5 in 803ffb0

	"base.header",
	"introduction",
	"base.activity+community",
	"base.repositories",

So as you can see, base.activity and base.community are actually combined into base.activity+community (because in the template it's actually the same file.

For this same reason it's not possible to directly to set community before activity though with extras_css and a good selector you should be able to target it and use flex-direction: row-reverse; if you wish to reverse the order of it.

For anything more complicated, the best solution is probably to fork this repository, patch the templates as you wish and use your fork instead in your workflow 👍

[RisingSunLight42]

Wow ! Thanks you for your quick response !
Is tht written on the repository ? If not, can I suggest to write this specification somewhere ? Because it's not natural to write base.activity+community (well, for me at least). 😅

[lowlighter]

No it wasn't written, I added a note to the "ordering content" section 👍
Thanks a lot for your feedback, this was indeed not very clear 😅