https://addons.mozilla.org/
As you can see, there are three add-ons recommended for first time add-on users highlighted, featured extensions, up and coming extensions, popular add-ons, etc.. You dive right in and one click takes you to the page for a specific add-on. There must be dozens of add-ons I can get to with one click from that page, some complete with descriptions about why I might want to use them on the page itself.
When I go to the Pale Moon add-ons page, I get this:
https://addons.palemoon.org/
There is not one extension linked to directly from that page.
These are the two pages you have to choose from when you navigate through the Pale Moon browser to Tools>Add-ons>Get add-ons
So, my suggestion is: Highlight Pale Moon add-ons on the https://addons.palemoon.org/ page the way Firefox add-ons are highlighted on the
https://addons.mozilla.org/ page.
I kind of get the feeling the Pale Moon add-ons page was designed thinking, "Well, we don't have many Pale Moon specific add-ons, so most people are going to go to the Mozilla page and get Firefox add-ons that maintain Pale Moon compatibility.". But we know that Firefox and Pale Moon are drifting further and further away from each other, with fewer and fewer cross compatible add-ons, and that the roadmap for Firefox means that there will be even fewer in the future.
Meanwhile, I assume one of the top goals of the Pale Moon project is to get many add-ons ported to or created for Pale Moon and hosted by the Pale Moon add-on site. And we are seeing more and more Pale Moon specific add-ons and people expressing interest in having them or making them as the number of Firefox add-ons compatible with Pale Moon dwindles.
*So*, to me in makes sense to drive traffic from the Pale Moon add-on site directly to, well, add-ons. Put some of the best ones there with logos and descriptions and stuff. Make it easy for people to find them and add them. Highlight what's there (Even if we have some super low level like 3, put all three up there). Maybe toss a simple link entitled "For developers: How to get your add-on approved and hosted by Pale Moon's add-on site" or "For coders: How to design and submit a Pale Moon add-on" at the bottom.
The front page of the current Pale Moon add-on site seems well intentioned, but a lot of casual users are going to see that and not immediately know where to find the Pale Moon add-ons. And, one secret of the casual Internet users is- they give up very easily. You want to put stuff right in front of people and make it as easy and simple as possible. Maybe even tempt them to download some extra ones they didn't know existed.
And if you want developers of extensions to come here and port their add-ons to Pale Moon, you don't want to make them find someone's email address or register for a support forum and start threads asking "How do I do this?" (Though I'm glad PM devs make themselves available that way). You want them to go to the add-on site, and just see a very clear link that tells them exactly what to do (guidelines, etc.) and how and where to submit it to. So, in theory, you could get an extension submission from someone you've never talked to before who just saw the site and followed the guidelines and sent it to you.
Basically, you want to make everything as easy as possible.
Right now, even going from within the Pale Moon browser, it is actually easier and more intuitive to find a Firefox add-on than a Pale Moon add-on. Should be the other way around, especially since some users will wind up clicking through the Mozilla site, see that a lot of the add-ons don't work with Pale Moon, and download Firefox to use them. We should be driving them to Pale Moon add-ons, add-ons that work with Pale Moon every time. And then saying, like if you can't find what you're looking for, rifle through the Mozilla site. And I think the time to start that is now, before the divergence between the browsers gets far enough to force a change later. Right now, it could be a subtle nudge, and ease the transition later. It'd also bring Pale Moon browser add-on user numbers up, which would encourage existing developers to keep developing, and start to demonstrate an audience to potential future developers who, say, want to port their old Firefox add-on and host it here while they are still developing an add-on for a somewhat similar code base and it'd be an easy port (In the future, they may be so far past developing for a code base similar to Pale Moon that it's a harder port than they want to deal with, or they may have given up maintaining their extension for Firefox and not be reachable or may not want to get back into the game- right now we still have time to get them when they are actively developing for Firefox and can port with less trouble. Maybe then even if they don't redesign their extension for Firefox later when Firefox demands it again, they keep developing for Pale Moon).
Anyway, it's just a suggestion. I won't be offended if people don't think it's the right way to go.
I'm just throwing it out there because I think it'd pave the way for more Pale Moon users using Pale Moon add-ons, more developers creating and hosting add-ons specifically for Pale Moon, and ease the transition when Mozilla pulls the rug out of their add-ons working with Pale Moon entirely (Which, let's face it, is coming- maybe not "intentionally" on their part, but we can see that they are deprecating the coding language that add-ons for Pale Moon and, until now, Firefox, have been written in- and even to this point changes in their browser mean that many of the Mozilla hosted add-ons don't work).
