Repository navigation
Home
Welcome. This wiki is the working manual for the YOUNGO Hub — the member and mission-control platform of the Youth Constituency to the UNFCCC. It serves three audiences: members who want to understand what the platform does and why, maintainers who run and extend the codebase, and operators who deploy and seed it.
If you only read one page, read How the Hub works. It explains the shape of the whole system — who talks to what, where the rules live, and the handful of decisions that everything else hangs off.
The Hub is one Next.js application backed by Payload CMS and PostgreSQL. It serves the public website, the member interface, and the internal APIs; there is deliberately no admin dashboard — staff work through the API, terminal scripts, or the database itself. Authority is not a field on an account: it lives in a single authority_records table of scoped, time-bounded mandates and participation records, and every permission check in the system derives from it. Decisions follow the constituency's real governance pipeline — proposal, consultation, decision, vote — and elections use a credential-based ballot rather than account-linked votes. Content is drafted, reviewed and published through the same API that the member interface uses, which is also the only write path available to the bundled MCP agent tools.
That paragraph is the whole system. Everything else is detail.
- Using the Hub — Member guide, Staff guide, Content and publishing, Notifications and delivery
- Building — Local development, Code map, Data and migrations, API reference, Testing
- Operating — Configuration, Deployment, Demo environments, Project maintenance
- Extending — Agent tools, Development context, Project status
- Commands run from the repository root unless stated otherwise.
-
DATABASE_URLexamples assume the local Docker Postgres on port5433. - Screenshots are avoided deliberately; the interface changes faster than the prose.
- British English throughout, matching the codebase and interface copy.