My current thinking is that we don't need plugins.json; we should just make index.html include (via a Liquid for loop), all the plugins who declare themselves to be part of the carousel. Of course, we still need JavaScript to randomly select which plugin of the carousel gets displayed first for a given page load.

More than happy to take a look at this since I wrote the original plugins pane for the Fiji website!

My current thinking is that we don't need plugins.json; we should just make index.html include (via a Liquid for loop), all the plugins who declare themselves to be part of the carousel. Of course, we still need JavaScript to randomly select which plugin of the carousel gets displayed first for a given page load.

I'm more than happy to try this, especially since it lets us do quite a bit of the work at build time (and we're not duplicating things, etc.). I'll investigate how much overlap we have between the two!

Been a bit busy, but I think I can get some work done on this today. Re:

My current thinking is that we don't need plugins.json; we should just make index.html include (via a Liquid for loop), all the plugins who declare themselves to be part of the carousel. Of course, we still need JavaScript to randomly select which plugin of the carousel gets displayed first for a given page load.

I've thought about this for a bit, and I actually think our best course of action is to create a plugins.json file. Inlining it into index.html would:

• significantly bloat the index.html's file size
• be a larger blocker for first contentful paint
• be larger dead weight if the user has disabled javascript

In addition, it maintains the plugins.json as an "active endpoint" that others can use to get more information about plugins, though I'm not sure if this is something that we want to support.

I think the only practical downside is a slightly longer render time as JS needs to be parsed before fetching the resource, but since the item is much lower than the fold I don't think it'll be too bad.

I'll draft a preliminary version, but switching between the two wouldn't be too tricky anyways! And of course, always free to get feedback on this proposal!