Using data-driven lists and static site generators

[ShaneCurcuru]

Is there an interest in planning for the future, and turning this into a static-generator site (I prefer the default GH-pages Jekyll, because it's zero maintenance) and making any lists be data-driven? That makes it much easier for maintenance, especially accepting PRs to list any new organizations (and doubly so when other folks start making submissions).

Similarly, what are the real objectives with the funder list?

• Criteria for inclusion? Any sort of funding? Any sort of organization (or individual maintainer) who is being funded? Do you want to bucket funders into categories, to separate the $500 a month here and there, vs. sponsors multiple foundations for Gold level?
• Metadata about organizations?
  • Thinking huge, you could ask to capture both who's funding (i.e. not just logo and website, but maybe ecosystem, type of company, etc.) and where the funding is going (i.e. a rough list of either foundations or projects the company funds).
  • Thinking normal scale, is there any interest in allowing companies to get a one sentence quote and officer attribution to their entry in the list? That'd attract a lot more companies, if they felt like they're getting a tiny bit of differentiation in their entry.
  • Either of these means setting up a data directory, storing the entries in yml/json/csv, and then having a template page for them - which is key for future maintenance ease.

[chadwhitacre]

I like where you're going! :) I think data-driven would be great when the scale justifies it. Criteria for inclusion are on the README. I do think we want some sort of maturity model eventually. My 2¢ is that we should keep things light for now in order to make it easy to get logos on board, and when we reach like 100 or so then it'll make sense to start looking at patterns and building out more metadata and filtering. I don't want to make it too cumbersome right now because that will make it harder to onboard companies.