RFC: Reject Static Site Generator Proposals

There are currently two PRs (#298, #284) that are asking about static site generators. In order to avoid a SSG bidding war. I propose that we don't add a static site generator to this project and if you were going to bless one that it be done in a separate repo.

This issue can almost be closed immediately but for the sake of people probably using AI to try and get small PR wins, I thought it might be important to

Reasoning: Ease of use

I think it's important that the information here be as easy as possible to add to. right now the workflow is:

1. add your conference to the csv (That's it)

Adding an SSG means that you will likely need to add a setup environment, and test the generation of the project.

More Maintenance than it's worth

I think if someone wants to maintain the website and all that goes with it, they should be welcome to - On their own terms.

Adding a site now means that css, user-experience, ui and more need to be added as concerns. It also signals to tool makers that may want to use this for their own tooling that they need to use the standard system for it.

My suggestion is that any request for a UI be rejected with a friendly reminder that the data is publicly available and this repo can be used as a data source for folks own projects

Read PRs #298 and #284 along with the repository’s current CSV workflow. No files or tests are named, so first determine whether the maintainers want a policy decision or a documentation update. Done means the SSG/UI proposal policy is decided and recorded, with this issue closed or updated accordingly.