@bo.near [Posted on DevHub](https://near.social/#/devgovgigs.near/widget/Post?id=1322) ## Idea: Documentation Work Group Meeting, Sep 13, 2023 ### AGENDA - Questions to cover - What is the current state of NEAR’s documentation? - What are the various resources available? - Who are the audiences for these resources? - Are they being managed? - If yes: Who is managing them? - What is the ideal state? - What is our “dream” state? - What do NEAR docs look like? - Where do they live? - Who is managing them? - How frequently are they being updated? - What content do they cover? - How do new docs get created? - How do we get from our current → ideal state? * Which docs should we continue managing? * Who will manage them/how frequently? * How will the Community Group participate in the creation and maintenance of docs? * Need to coordinate across all the groups * How do we audit the current state to tackle the above questions? - Who are the audiences for the docs? - Damian: Developers. Not trying to do marketing / selling. We provide code, examples, explanations. - Bo: Every developer tool on NEAR except BOS ### Action Items * Damian: go through all repos, have them update documentation for the latest release. Fix the missings. Bo: I’ll talk to these repo owners. * A list of all the current documentation resources. This would be helpful for the Devhub Homepage too. * List of all the pages and their owners. Plus a wishlist of new pages and documentation projects we want to see happening. * Key takeaway is that we need to clarify – who owns what? See what they’re planning and how others can get involved as contributors. * This is an opportunity to revamp. * Ayoung to get the google sheet started and create the next meeting. ### IN ATTENDANCE @ajeon.near @efiz.near @jass.near @bo.near @bearmans.near @james.near and Damián Parrino ### Questions James: confusion of which path of docs. can be mitigate by convo between different groups Difference between create-react-app and near-api-js? (it’s unclear on the DOCs, there is no longer references to BOS, confusing and hard to find) Jas & James: create-near-gateway. customized gateway could be easier than building Should we in the meanwhile create an aggregated documentation resource page or maybe just put it on docs.near.org Who owns the current tools (that we need documentation for)? How do we go about having developers document their own new features/changes? (Bo and Damian will reach out)