Prerender sponsors for READMEs

[nzakas]

What problem do you want to solve?

Right now, we have multiple repos that pull in the raw data JSON files for sponsors and then generate the same HTML to insert into the README. This requires us to duplicate a bunch of logic in every repo where we want sponsors displayed.

What do you think is the correct solution?

Generate the sponsors sections (headings and tables) and store in a file on the website so each repo can just fetch the file and insert it directly into the README.

Participation

• I am willing to submit a pull request for this change.

Additional comments

Looking for a volunteer for this.

[amareshsm]

I will work on this. This repository will include the logic to generate and update a file with sponsor content. In the other repositories, we will update the update-readme.js file to fetch the content from this centralized file. let me know if my understanding is correct. Also, could you clarify what you mean by "store in a file on the website"? I'm not entirely sure I understand.

[nzakas]

Yes, that's correct.

What I mean is, we can build the file so it's accessible via https://eslint.org/sponsors.md.

[nzakas]

Or, I suppose we could also just keep the file in the repository like we do with the data files now.