I am Krishna Kumar, a Computer science undergrad at KIIT. I have experience with JS/TS with React. I have made some small Pull requests before. I am interested in the "Improve plugin search and discoverability" project and soon write a draft proposal for that. I have some doubts regarding the projects which I asked on Discord here, here Looking forward to work with the team this summer.
The current site is the /readme folder which is build and hosted with GitHub, but the plugin route seems to be a large project which can grow large as the number of plugins grows. So I was thinking of a react web app with dynamic routes for every plugin. Can I make it? Even if we make a static build we have to build it whenever a new plugin is added, I will fix it with react, as a new plugin is added the next second it can be visible to the user. As mentioned the whole project will be in typescript and GitHub Actions for CI/CD.
If I get something wrong or you want do to something different just let me know, this is just my opinion.
All the above can be done using the info from the plugin repo, in particular using manifests.json and stats.json. You would use this to implement the above functionalities. Moreover, the joplinapp.org pages should be dynamically generated using a script and this should be integrated with CI.
This is written on the Idealist page. Does that mean the plugin route should also go under the joplin/ website repo ??
or it should be separately made, hosted, and mapped to the joplinapp.org/plugins route