@nearmax.near [Posted on Developer DAO Board](https://near.social/#/devgovgigs.near/widget/Post?id=557) ## Idea: DevHub Personas and User Stories In this post I would like to describe why DevHub communities features is important, who it is blocking, and what improvements we need to further add for it. # Marketing Persona As a marketing person/team/organization working with DevHub or any other NEAR organizations like NEAR Foundation or Pagoda, I would like to help bring awareness to NEAR developer ecosystem. I am able to organize marketing campaigns however I need the following: * I need to know where to send developers from my marketing campaigns, and I need to understand what page these developers are going to be landing on, to craft a high quality marketing message; * I myself need to understand the specifics of the community that I am sending developers to. E.g. is it deep tech, where do I find these kinds of developers, do we have a lot to show and capture the attention of the developers or is it an early-stage community, how crowded this community is already, are there any relevant events and milestones that I can capitalize on in my marketing campaign, etc. * I need a way to craft a marketing message. The technical content of the community might be too deep for me to understand myself, so there should be a place where the messaging of this community is already laid out in accessible to me form. # BizDev Persona As a person/team/organization negotiating deals with/for NEAR ecosystem projects I need to understand strength and weaknesses of NEAR ecosystem and how to sell it to third-parties. * I need a place in the NEAR ecosystem where I can send partners to familiarize with the state of Zero-Knowledge, Infrastructure, Protocol, etc; * I need to be able to educate myself quickly on various subject matter topics in the ecosystem; * I need to know what was achieved and has happened in certain areas of the ecosystem in the past months, 3 months, a year; * I need to know key people behind top ecosystem initiatives so that I can introduce them to the partners to facilitate networking; * I need to know about upcoming events that I can point potential partners to. # New Developer Persona As a new developer considering engaging with NEAR ecosystem, I am interested to know what’s going on without committing too much of my personal time doing digging in numerous forums, posts, etc. * I need one place associated with my area of interest, e.g. JS, where I can discover everything in NEAR ecosystem relevant to it; * Depending on my persona I might prefer async method of familiarization, like reading lots of docs, or I might prefer real-time chats with existing developers. Both options should be available to me; * Ecosystem needs to be engaging so that when I post a question, an idea, a PR, or an Issue someone at least acknowledges it; # Existing Developer Persona As an existing developer persona I want all NEAR resources to be at my fingertips. I don’t want to be looking around for all JS-, ZK-, Rust-related libraries and documentation. I also want to have an immediate access to the channels where my questions are immediately answered. I also need a clear understanding on what is the next step on my journey from generating ideas, to implementing them, assembling the team, soliciting support, etc. # Proposed Solution num. 1 Each DevHub Community (Zero-Knowledge, Protocol, Education, Events, etc) will have the following tabs: * **Overview.** Provides a mind-map of that community. What does it do, projects to brag about, vision/mission/values kind of entry or messaging explainer. As the scope and the number of projects in the community grows this page becomes more akin to `Awesome*` type of page, see: https://github.com/mbasso/awesome-wasm * **Discussions.** A.k.a "Slow-read". Posts from DevHub with a specific label, e.g. `zero-knowledge`, `protocol`, etc. This is similar to themes/topics feature of Zulip where posts are grouped by their theme. * **Channels.** A.k.a "Fast-read". Multiple tabs, one per Telegram channel, that sync messages in one direction from the corresponding Telegram channels. This is to ensure that developers exploring the community can switch between Overview, Slow-read, Fast-read, boards, events, etc without leaving DevHub. In the future we can add bi-direction message sync, where messages posted in one of the "Channels" tab will be re-send to the corresponding Telegram channel by a bot account. * **Boards.** As many boards as community needs, e.g. for proposal review process, events planning, funding approval. * Separately if this community also has a Github project board somewhere, Github issues/PRs linked from that board will be reposted to DevHub together with the corresponding labels. These labels, like `S-draft/needs-author-revision` can define the columns in this board. * **Teams.** List of people with specialized roles, e.g. Work Group member and a corresponding access control rights, e.g. ability to use `wg-protocol` label. * Once we link Telegram accounts with NEAR Discovery profiles, we can also just list all people who have any activity in this community and their corresponding badges. Then we can rename this tab to **People.**. But without linking with Telegram profiles this tab will be very empty and will create a wrong impression of community inactivity; * **Events.** Here we need to list both community events with their recordings and summaries, as well as any third-party events relevant to this community, e.g. see Rust calendar for inspiration: https://calendar.google.com/calendar/embed?showTitle=0&showPrint=0&showTabs=0&showCalendars=0&mode=AGENDA&height=400&wkst=1&bgcolor=%23FFFFFF&src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com&color=%23691426&ctz=Europe%2FMadrid * **Badges.** Each community can have its own way of rewarding contributors as well as a way to make fun and create goofy rewards (e.g. "I said so" badge for submitting an issue that later led to an accident). This is where community can get creative.