Indeed, that would be very welcome.

I suggest the following:

1. Promote CustomCSS and CustomJS to core extensions (i.e. move the code from the Extensions repo to the core FreshRSS repo)
2. For system extensions (not relevant for CustomCSS), save extension data in data/extensions-data/{extension-name}/ (some initial work was done in Change CSS load order to help CustomCSS extension FreshRSS#1547)
3. For user extensions (relevant for CustomCSS), save extension data in data/users/{user-name}/{extension-name}/

Would you feel like sending a PR? (maybe @Frenzie could help?)

I'm not really sure what that would entail without investigating, but happy to answer some questions if asked.

Thanks for the reply.
It will take me a long time because I'm a PHP beginner, but I will try it.
I will decide which approach to adopt after a better understanding of the code.

BTW, any approach would lose compatibility with existing configurations, is that a problem?

A few points:

• If we promote CustomCSS and CustomJS to core extensions, they will get a slightly different name, and both the old and new extensions can co-exist for some time, without breaking anything

• In any case, we could consider copying automatically from the old location to the new

• https://github.com/FreshRSS/FreshRSS/blob/edge/p/ext.php might have to be adapted a bit

OK, then I'll avoid duplicate names so that they can be used at the same time.

I submitted a pull request FreshRSS/FreshRSS#6267.
Please review.