We have an internal notion page where a lot of valuable planning and process content lives. Some of that might sometimes be of interest to the current/future community.
It also makes our lives easier when we can share/link people to strong content that addresses their questions e.g. "why is this inactive" "what are you guys currently focused on" "what is your roadmap".
Another benefit might be more motivation for us to keep the content quality up. We've been pretty good so far (?) but it is demanding to be sure. But if we know there is greater value beyond just an internal 1-2 people, well, that means something.
One tradeoff is that it adds overhead for us internally to keep track of private/public content. Generally it doesn't matter, but its also easy right now because we just don't have to think about it (there are two exceptions in the tech docs table where pages have been made public).
Possible content we can consider:
tech docs
roadmap
sprints
quarters
teamflow
So concrete things we need to do:
General decision on if we want anything public
If so, what parts? Some, most, all?
For the chosen content, how do we re-structure our Labs page downward (think of it as as tree of content where the labs home page is the root) to accommodate the mix of private and public.
We have an internal notion page where a lot of valuable planning and process content lives. Some of that might sometimes be of interest to the current/future community.
It also makes our lives easier when we can share/link people to strong content that addresses their questions e.g. "why is this inactive" "what are you guys currently focused on" "what is your roadmap".
For example maybe we want https://github.com/prisma-labs/issues/issues/9 to be publicly accessible. Or perhaps a hiring table about open opportunities.
Another benefit might be more motivation for us to keep the content quality up. We've been pretty good so far (?) but it is demanding to be sure. But if we know there is greater value beyond just an internal 1-2 people, well, that means something.
One tradeoff is that it adds overhead for us internally to keep track of private/public content. Generally it doesn't matter, but its also easy right now because we just don't have to think about it (there are two exceptions in the tech docs table where pages have been made public).
Possible content we can consider:
So concrete things we need to do: