• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
Friends With BenefitsFriends With Benefitsby0x2afE4De9D1C679E42C03649D86FFDDDc07751AE6kirkusmaximus.eth

FWB Wiki

Voting ended over 3 years agoSucceeded

Team: @kd, @naomi (among many others)

Abstract


The FWB Wiki started as a community led knowledge base for all things FWB, providing a static place for important member information. With this proposal we want to refresh the Wiki to make it up to date, assign internal team members to keep it that way, and establish a seasonal contributor team to help maintain the FWB and field questions from the greater community to determine what else would be beneficial to add. 

The goals are:

  1. Update the existing Wiki (see: https://fwb-wiki.vercel.app/) to become a hub for FWB documentation and FAQs 

  2. Establish a method for seasonal contribution and internal team maintenance, with the internal team owners updating their relevant sections with the most up to date information

  3. Set a schedule to keep Wiki relevant as the DAO evolves 

  4. Relaunch the Wiki with this proposal and have establish funding to support it staying updated for 4 seasons

Motivation


Community value is built through community knowledge. But with Discord as the main information hub, key information is hard to find.

That is why a team of FWB community members began to work on the FWB Wiki last year. After this initial launch, we realized a need to formalize it through this proposal to keep it updated as a relevant source of information for members. 

This proposal aims to set up a sustainable method for the Wiki to remain updated and to provide an access point for members to help add to and amend the wiki. 

Impact on FWB community


Our aspiration with this proposal is that the wiki serves as a useful tool for both new and existing members, that it's a 'source of truth' where anyone can find up to date information allowing the ease of understanding and  navigating the DAO.

In establishing a method for maintenance, we would also be creating a low bar of participation for FWB members to get involved and contribute to the maintenance and growth of the wiki. Knowing how things work at FWB increases new member participation and contribution to ongoing initiatives.

Overview


In mid-2021, a team of 7 FWB members got together to build the current wiki page. It was built on Notion with onboarding members as the target audience. The team set about collecting information, writing content, and formatting it into a knowledge base.

Several opportunities arose during that process:

  1. Maintenance --- Some of the content would need to be regularly maintained in order to be accurate and, other than manually, we didn't have a system in place for that (for example, the Seasons page)

  2. Expansion --- There was plenty of content to capture and room to continue to grow this wiki to be a valuable asset to the DAO. As a starting point, we stuck to content that would be most helpful to new members onboarding.

  3. Fact checking --- In order to maintain accuracy, we needed fact checkers. The initial group of members were able to check each other's work ad hoc, but having a formalized process to ensure accuracy and solid proofreading was lacking.

We migrated the wiki to Gitbook - where it currently lives.  

Details


Discussion

Importance: organization, growth, enabling a good experience for the community

FWB has heaps of valuable information, but our main information hub is Discord, which is not the greatest place to find the right information in a useful format. A dedicated knowledge base such as the FWB wiki will enable growth, result in more organization within the DAO, and a better experience for the community. 

For the wiki to remain useful, information needs to be maintained and updated over time. By establishing a way for contributors to add to the wiki, members can have an avenue to ask questions and for the main wiki team to be able to monitor and synthesize these ad hoc questions to determine what would be best to add to the greater wiki. The contributors for this proposal were selected based on their involvement in the inception of the initial wiki and their contributions to push it forward to the stage of this proposal. 

We want to create a public works channel for the wiki to be a general place for everyone to ask questions, and for the core wiki team to know what needs to be updated or added to the wiki to maximize its benefit for community members. Every season there will be a group of contributors who will be tasked with monitoring this channel, deciding what will be added to the FAQ section in the wiki, and what to flag to FWB staff to update on their ends of the Wiki. 

Roadmap

  1. Migrate the current Wiki to FWB Github 

  2. Establish a seasonal budget for contributors 

  3. Establish a method for ownership of maintaining content between contributors and FWB team

  4. Internal team & contributor team do a full refresh of their owned Wiki sections (See breakdown below for ownership division) 

  5. Token-gate the Wiki for all members (currently 5+ FWB)

  6. Set up a public works channel  

  7. Relaunch the FWB Wiki 

Wiki Refresh Structure & Ownership

Getting Started **Membership/Brand

Code of Conduct *Justice

Discord Channels Navigating*Membership/Brand

  • Overview *REMOVE

  • Discord Bots *REMOVE

  • Voice Chat Channels *REMOVE

Products and Programs *Product/Governance/Events/Membership

  • Overview *REMOVE

  • Co-Pilots *REMOVE

  • *ADD Membership (within page detail Host Committee, Co-Pilots, Category Leads) 

  • Fellowships *REMOVE

  • Hackathons *Change to Garage + detail programme

  • *ADD Event Keys 

  • *ADD Gatekeeper

  • *ADD Member Directory 

  • *ADD Digital Events

General FAQs *Community maintained

  • About FWB

  • Becoming a member

  • Application process

  • Getting started

  • Onboarding

  • Governance

Events Calendar *REMOVE

Voice Chat Archives *REMOVE

Glossary *MOVE TO FAQ

Governance *Governance 

Proposals *MOVE to subheading under governance

Seasons *Brand

  • Current season

  • Season history

FWB Cities *REMOVE

Org Chart *REMOVE

Teams FAQ *REMOVE
Above is proposed structure and ownership, might shift slightly as Wiki gets reworked and we find new ways to organize/add to this base.

Looking forward

Our aspiration is to create a robust, constantly evolving and growing Knowledge Base for Friends With Benefits that is a foundation for all the DAO's information.  Our aim is to activate contributors to keep information relevant and up-to-date and add new pages over time.

Outcomes & Success Metrics


We will enable page view count tracking and bounce rate metrics for the wiki and each of its sections. At the end of each season of this proposal, we will draft a breakdown of where members (and non members once token gating is determined) visited the wiki and what sections seemed to garner the most traffic overall. We will use these learnings between the first and second season of this wiki proposal to refine what we should add or amend from our first wiki iteration.

Budget for 2 Seasons 

Retroactive payments for Migration Work

  • 5 FWB for Baumaus for Nextra Install and migration of Wiki content to Gitbook

Management & Maintenance Contributor Budget

  • 15 FWB per season, per contributor (max 3 contributors per season) 

  • Total: 90 FWB

Timeline

Weeks 1-4

  • Migrating the existing Wiki for FWB owned github

  • Assigning sections to be updated by internal team 

  • Complete first draft of updated sections

Week 4-5

  • Review and edit wiki sections

  • Contributors finalize initial FAQ contents 

Week 6-7

  • Create public works channel for wiki 

  • Implement Wiki token gating for new version 

  • Relaunch the wiki in discord and through a general marketing campaign 

  • Ongoing

  • Seasonal updates by FWB Team 

  • Monitoring of public works channel by contributor team, and regular updates of FAQ section

Off-Chain Vote

Yes - Fund FWB Wiki
8.2K FWB98%
No - Don't fund FWB Wiki
170.15 FWB2%
Download mobile app to vote

Timeline

Aug 03, 2022Proposal created
Aug 03, 2022Proposal vote started
Aug 09, 2022Proposal vote ended
Jul 09, 2025Proposal updated