jQuery is used for handling Ajax stuff in code/public/js/orct2p.js
We can replace it with native JS

When a plugin's description links to an image with a relative path, the image won't show up.

Example:
http://openrct2plugins.org/plugin/MDEwOlJlcG9zaXRvcnkzMzI1MDA3OTY=/title-sequence-editor

This description's image links to images/screenshot.png. Since it's linking to a local repo's image, it works fine in GitHub, but it won't show up in the the Plugin Directory.

We could check for relative paths, and then complete the URL to make it absolute.

Bootstrap has its own classes to properly handle style of tables:
https://getbootstrap.com/docs/4.5/content/tables/

The problem is that the Parsedown library doesn't output the classes required by bootstrap to properly style them, leaving us with this monstrosity:

There's easy 2 ways of fixing this:

1. Apply the bootstrap styling to html tags (<table>, <thead> and so on) instead of specific classes. This will affect every table in the website, but i don't think that's an issue

2. Modify the Parsedown library to output the correct classes along with the html tags.

I prefer the 1st option as it doesn't rely on modifying the library and won't have a problem if it's updated and whatnot.

i.e. https://openrct2plugins.org/plugin/MDEwOlJlcG9zaXRvcnkyNjc3NjU4NTM=/openrct2-ride-price-manager

Shows:

Meanwhile on the repo:

I received an email from GitHub recently stating:

We noticed your personal access token, openrct2plugins_prod, has an outdated format and was used to access the GitHub API on May 20th, 2021 at 04:00 (UTC) with a user-agent header of Dunglas's minimal GraphQL client.

We recently updated the format of our API authentication tokens, providing additional security benefits to all our customers.

In order to benefit from this new format, please regenerate your personal access token, openrct2plugins_prod, using the button below.

(Regenerate your personal access token Button)

To understand more about this change and why it's important, visit https://github.blog/2021-04-05-behind-githubs-new-authentication-token-formats.

We encourage you to reset your other authentication tokens as well, or revoke any that are no longer needed. This applies to integrations (such as OAuth Apps and GitHub Apps) as well as personal access tokens. For more information on reviewing your authorized integrations, refer to https://docs.github.com/github/authenticating-to-github/reviewing-your-authorized-integrations.

Thanks,
The GitHub Team

Need to dig deeper into this, and see if there are any changes needed in the code, or if I can just regenerate the tokens

So I have made a package manager for openrct plugins
https://github.com/marvin1099/OpenRCT-Plugin-PM
It works by webscaping the webside
openrct2plugins.org
and at first I didn't think an API would be that important, but it would make the package manager more elegant and the plugin website more versatile.
I already talked about it in Discord and Saadbruno asked me if he should implement it.
At this point it may or may not be worked on, I created this topic mainly so that the status of the implementation can be easily verified.
If there is no interest in this feature, you can of course say so or close the issue.
Btw. "lastupdate" wold be a unix timestamp in this example.
Here is my idea of how the api could look like:
Reqest --------

https://api.openrct2plugins.org/?getjson=true?query=grass?maxresults=10

Or i could be reqested like this -------

https://openrct2plugins.org/?api=true?getjson=true?query=grass?maxresults=10

Result -----
{
    "resultsnr":"3"
    "results":[
        {
            "pluginname":"openrct2-auto-mow",
            "plugindataurl":"https://openrct2plugins.org/plugin/R_kgDOHLFjjQ/openrct2-auto-mow",
            "plugingeturl":"https://github.com/PhasecoreX/openrct2-auto-mow/releases/latest",
            "lastupdate":1694292469
        },
        {
            ...
        },
        {
            ...
        }
    ]
}

Need to investigate, but this plugin for example, doesn't show any description, despite the repo having a README.md file

As discussed in Discord, would be cool if developers could submit custom information to the plugins site along with their repo, to allow manual overrides of plugin title, image and set a direct link to the plugin JS file.

There's a few ways we could do it. We could have a login system with user accounts, so they could register and edit their own plugins. I'm not really a fan of this idea.

Another way we can do it (thanks to Oli414 for the suggestion) is to allow plugin owners to have a file in their repo with information we can use. I think we go with this one.

So we need to:

• Choose a markup language
• Choose a file name
• Implement all the code and DB changes to make it happen

Currently, when a plugin has a custom license, we link to https://choosealicense.com/licenses/other/, which is a 404

I also think we should rename "other" to "custom", it might be a better definition

code/bin/update_plugins.php is the script we run when updating plugins via cron.

When an existing plugin listed in our database gets deleted from GitHub, this script stops excecution:

updating plugin for Topodic/openrct2-scenery-scatterer-plugin
{"status":"error","message":"Error when adding plugin "}make: Leaving directory '/home/saad/dev/openrct2_plugin_repository/docker'

Wether we should delete the plugin from our database when it's missing from github or not is another question. But this script should keep updating the rest of the plugins regardless.

The website should show which license the plugin you're viewing uses, preferably even on the list overview but the plugin detail page would be good enough.

I for one don't want to use any proprietary plugins (if they will ever exist) so I'll have to filter by FOSS only.