Developer's page

[BrittanyBunk]

I thought up the idea about a developer's page - for those who want to add to the map to help it along. Turns out this idea has been going for a long time. Maybe we can brainstorm here how it'll look? Here's some ideas according to ethan: "At the very least, the beta website should link back to GitHub issues and our Slack. The API documentation should be published to the website. And as you point out, we should have a more comprehensive contributor guide. The challenge is that things are in transition with so many old and new versions, so a bit complicated."

[ezwelty]

To add to my quote above, it might be worth writing a custom README for our GitHub organization page (https://github.com/falling-fruit), describing the current state of affairs and how to get started running the full Falling Fruit software stack locally. At the moment, this requires three repositories: https://github.com/falling-fruit/falling-fruit (for the database), https://github.com/falling-fruit/falling-fruit-api (for the API), https://github.com/falling-fruit/falling-fruit-web (for the beta website)

[ezwelty]

A while ago, I created a custom organizational README and updated the documentation for the repositories to make things easier for people: https://github.com/falling-fruit

We also now have an active Slack workspace and aspiring to a ~monthly community call.
https://join.slack.com/t/fallingfruit/shared_invite/zt-1oh1paonq-XJ7dBHPapv6uuBTc93~4UA