TLDR Remaining work to be done are sorted into two sections, Frontend, and (CI / documentation / json.) Some of these points are definitely discussions.

## 1. Frontend / React
Lots of room for near-future changes, and far-future changes.

<strong> Smaller changes </strong>
- Some logos (e.g. netflix, airbnb, lyft) require express written permission, a superset representative could seek these out. Can put out PRs to address logos without strict requirements
- Dark mode could be prettier, border color change maybe?
- Currently use collapse accordion (one section expanded only). Could consider changing it to expand as many as you want, but then I would also think about adding (collapse all, expand all).
- Could consider adding a list version - some people just prefer minimal views to be honest.
<strong> Larger changes </strong>
- In the expanded sections, it might make sense to sort the entries to show those with logos first (alphabetized) and then just do a list of the rest of the org names, since the cards with just text might take up an overwhelming amount of space. So a card wall and a list in each section
***Plan: create a second PR to demonstrate and see what is preferred*
- Eventually: mark some as "featured" to display some superstar logos on the home page. Could use antd carousel like index does
- The Global nav space is going to get tight in the near future. Think it's worth adding this as a section within the Community Resources page, or is it going to be just way too big?
***Dependent. To be fair, there are a lot of companies/logos. Either way, the inTheWild.tsx file is incredibly compact and can be easily copy pasted into the index file to go right under the databases section*

## 2. Json / CI / Documentation
- Create a JSON file (easy to see nested sections) -> quick convert to js object
- Rewrite "first-contribution documentation" so contributor adds their JSON to the json file directly
- Add pre-commit and/or CI check to ensure json is safe to merge; probably should use AJV as it is used elsewhere (alternatives like JOI)
- Add CI to also convert json back to md to make a readable accessible list for the readme file.
- Have a script (maybe an npm command in the docs site?) compile/insert that section into the readme. One way or another, it would seem we can find a way to automate this with CI to make sure the readme stays current with these updates.
- <strong> Issue with js writing/fs, docusaurus cannot access server files directly, probably try a custom plugin, suspect just a prebuild script in docusaurusconfig would not work</strong>
- Reason I believe so is I tried an approach of pulling the opposite way (that is from readme.md -> json) and I think there's some circular work