Request a feature

Got an idea for the sites or this handbook? Propose it. The community grows by people asking for what they need and then, often, helping build it.

Where to propose

Open an issue on the website repository and describe the idea. That is the same place bugs go, just make it clear this is a proposal rather than a fault.

What makes a good proposal

• The problem first. What are you (or the people at your events) trying to do that is hard or impossible today? Describe the need before the solution.
• Who it helps. Organizers, attendees, a specific country, everyone?
• A rough idea of the solution, if you have one. It does not need to be detailed or final.
• Examples, if another site or tool does this well.

Common requests we welcome

• Add a new country. If you want to run the community in a country that is not live yet, say so. Each country needs a domain (or DNS we can point) and ideally a local maintainer.
• A new event type beyond hackathons, meetups, and unconferences, worth a blueprint of its own.
• Site features: something on the events page, the member directory, the stats, or the way languages work.

How proposals get handled

There is no big roadmap committee. A maintainer will respond on the issue, ask questions, and either pick it up, park it for later, or explain why it does not fit. If you are willing to help build it, say so. That moves things along a lot.

Keep in mind the project’s guiding constraints: the sites are static and privacy-first, the domains are borrowed so everything is built for a clean exit, and identity is anchored in AT Protocol rather than any one domain. Proposals that respect those tend to land quickly.