META - Make this repo the best place for the community content

[moul]

This repository should be more actively used and become the main hub for community content, including curation, recipes, tips, and more. The goal is to empower the community and designate it as the "unofficial/community powered" hub to facilitate faster content merging with fewer restrictions.

In my opinion, this repository should be a top choice for individuals who are not very tech-savvy to collaborate and earn points. It also helps them understand the project better and make significant contributions in the future.

People should know that contributing is incentivized through Game of Realms and the concept of proof of contribution and evaluation DAO.

I believe increasing activity in this repo should be a key goal for the devrels and marketing teams in the next quarter.

---

To-do list:

• Set up the FAQ.md here (refer to issue Add Gnoland FAQs #41).
• Integrate this document into docs.gno.land (bonus: consider moving Docusaurus to this repository to keep gnolang/gno focused on raw technical content).
• Recognize the top community contributors in the contributors DAO and invite less tech-savvy individuals to join by assisting in coordinating, filtering, translating, fixing, and connecting the dots.
• Consider having a call with community moderators or incorporating a dedicated section for them in one of our meetings.
• Once promoted, grant them the right to approve pull requests and establish a merge approval process with a minimum of N reviews (2 or 3?). In the meantime, let's use the core team, devrels, and core contributors as primary reviewers.
• In the long run, aim to have recurring articles like the "the more you gno" series or "fresh news from the community, by the community, for the community" managed here.

---

At the end, here is the suggested overview of content areas and scopes:

• gnolang/gno: Technical documentation and discussions.
• gnolang/awesome-gno: Community discussions, recommendations, recipes, documentation, introductions, etc.
• gnolang/hackerspace: Less official but still technical, primarily for partners and the core team, but open to any hacker building things.
• gnolang/meetings: The space for meetings, transcripts, discussions, and chats. It is managed by bots/automation/humans, but mainly intended to be written by staff and read by the community. However, it makes sense to allow people to open pull requests to fix typos and assist in content reorganization (we could give it a try).