@tomavatars Awesome idea. I see what you described happening a lot with blockchain/cryptocurrency projects where the developers will open up their internal Slack channels to the public. This way you can see all the issues, bugs, and features being worked on by the core team. Additionally, you can follow commits and pull requests on GitHub, but this is not as freeform as a document surface.
More importantly, getting creators to share their projects has multiple benefits:
-
Public Knowledge - Your video game project would be like contributing to Wikipedia, and since it’s public, anyone would be able to @reference that project to use in their doc. Let’s say the name of your game is “Tom’s Adventures.” One could then write something like
@Tom's Adventuresto get the full record of your game or=[Tom's Adventures].[Release Date]to get a specific field about your game. (Excel is rolling out new data types this year which is similar to this concept). -
Open Source - More innovation comes from projects that are shared to the public with multiple contributors.
-
API - Building off of public knowledge, creating an endpoint for your data makes it easier for others to incorporate your knowledge and resources into their own projects (hint hint: Zapier integration)
.