So I have been thinking about it a little bit over the last few days. We have quite a few people building production level apps and scaling them up to thousands of people. Apps built with Redwood. We should be publicizing this as much as possible. It gives off inspiration and really lets newcomers see what is possible with redwood more than any demo app or tutorial could ever do.
Things I think we should focus on first
I think the best thing we can do feature wise for now is keep this simple. An app showcase where makers can submit their projects. Maybe a little bit about them links to the site and social profiles. Additionally we can add an admin backend to manage submissions. For the first iteration I think leaving tutorials and stuff is out of scope and we shouldn’t try stepping on the toes of what the team is doing with cookbooks.
I don’t think that is necessary I think the redwoodjs twitter account is fine and official.
Tutorials to do a bunch of stuff in “production”?
I think this is something separate. But have some ideas around this and improving this with more cookbook related stuff. The current tutorial stuff is great. What I think is missing is running your app in production, monitoring, scaling. But thats for a different time.
How can we maintain this and provide as much value as possible.
Well this is a redwood project so the redwood makers and contributors should be in charge of maintaining it. Redwood is an open source project so this site should be too.
We can use this project as a stepping stone for people looking to get in to redwoodjs or contributing to open source. I think this can hit two birds with one stone. It allows people to contribute to an open source project and dip their toes in to building with redwood and is beginner friendly. It can be intimidating to contribute to redwoodjs-core because of how big it is. This is the type of project that doesn’t really have to be done ASAP and can keep getting iterated on especially if we get the core “showcase” done.
This might be a little over the top but would be kind of cool for community engagement. In todays contributor meetup @giannelli.tech talked about people looking for mentorship. We could use a project like this to host scheduled office hours / pairing session where someone looking to learn redwood and contribute could drive and someone on the team could help them navigate building a feature out.
In my opinion we need a site that is built with redwood that is maintained and iterated on. A living app. A production level app. Something better than the example blog or example todo, something that uses real data and receives more than just package updates. And is built with redwoodjs. I think this type of redwoodjs app/startup showcase could be a really good starting point.
@barakcodes I am down to help kick this off with you do we want to take @thedavid offer and spin up a repo under redwood org?