The documentation says NomNom was originally created at the request of the Glasgow 2024 Worldcon leadership with the intention of producing a solution suitable for any Worldcon that chooses it. The public site is not the Hugo Awards homepage and does not indicate that every convention uses the software. Its case-study value comes from making specialist fandom infrastructure understandable to administrators and contributors.
Case Snapshot
- Website: nomnom.fans
- Category: open-source awards nomination and voting documentation
- Audience: Worldcon administrators, election teams, developers, and technical volunteers
- Public features: administrator guides, developer setup, workflow documentation, trust information, code of conduct, search, and a linked GitHub repository
- Activity checked: September 4, 2026
The Homepage Defines Scope Before Features
NomNom begins by explaining the process it supports and the community context around it. It describes integration with convention registration, customizable convention extensions, administrator control over ballot presentation, validation tools, and scheduled reports. That level of framing is valuable because most readers will not arrive with a complete mental model of awards administration.
Good technical documentation should answer “what is this?” and “who operates it?” before listing configuration details. For a community project, it should also say what the software does not decide. NomNom's documentation notes that eligibility rulings belong to administrators even though the system can record those rulings.
Administrator Guides Follow the Real Workflow
The navigation covers consultative votes, canonicalization, starting a convention, nominations, paper ballots, Hugo voting, and packet management. The nomination page connects implementation behavior to the applicable WSFS Constitution, including nomination limits and the E Pluribus Hugo process.
This is more useful than documenting screens in isolation. It links interface behavior to the rules and decisions that give the interface meaning. Other fan-run organizations can apply the same pattern by organizing documentation around membership, submissions, review, voting, publication, and appeals rather than around an internal database schema.
Open Source Makes the Operating Model Inspectable
The site links directly to the WorldconVotingSystems/nomnom repository on GitHub. During review, the repository displayed more than 1,000 commits along with source code, tests, security information, a license, a code of conduct, and development tooling. Public code does not automatically guarantee security or correctness, but it gives qualified contributors a way to inspect and improve the system.
For volunteer communities, maintainability is as important as initial delivery. Setup instructions, realistic seed data, tests, issue tracking, and a documented contribution path reduce dependence on one person who remembers how everything works.
The .fans Domain Fits Community Infrastructure
NomNom is a playful project name, while `.fans` explains the social setting in which the tool exists. The address creates a memorable documentation home outside a single convention's temporary event site and can remain stable as different organizers evaluate or reuse the software.
This expands the idea of a .fans website. It does not have to be a news feed, fan club, or merchandise store. It can be the technical layer that helps a fan-governed institution operate.
Five Lessons for Community Software Projects
- Explain governance alongside features. Readers need to know which decisions belong to software and which belong to people.
- Document the complete workflow. Administrator tasks should follow the sequence of the real event.
- Separate reusable core from local configuration. Convention-specific presentation can change without fragmenting the main project.
- Publish contribution and conduct expectations. Technical openness needs social rules as well as source access.
- Design for handover. Tests, reports, seed data, and setup instructions help future volunteer teams continue the work.
Trust Requires More Than Public Code
An awards system may process member authentication, nominations, ballots, eligibility decisions, and unpublished results. That creates requirements around least-privilege access, encryption, audit logs, backups, incident response, retention, independent testing, and separation of duties. Public repositories and documentation support scrutiny, but a specific deployment must still be secured and reviewed.
The project also publishes a Contributor Covenant code of conduct, creating a clear route for community standards and enforcement. Operational teams need parallel procedures for election complaints, data-access requests, suspected compromise, and post-event deletion or archiving.
Practical Takeaways for Fan-Run Institutions
Start by writing down the governing rules and the human decision points. Then map each software screen and report to that process. Keep sensitive operational documentation separate from public contributor guidance, but publish enough architecture, security contact information, and change history to support informed trust.
Communities establishing a long-lived project identity can consult the .fans overview, review common questions in the .fans FAQ, and check names through the registration page. Governance, security, election law, and trademark questions need specialized review.
Conclusion
NomNom.fans is a strong example of fandom expressed through infrastructure. Its public documentation connects software features to convention administration, voting rules, contribution practices, and trust. The durable lesson is not that every community should build election software. It is that when volunteers run consequential processes, clear documentation and governance are part of the product, and a stable fan-centered address can make that shared work easier to find.