WorldconVotingSystems / WorldconVotingSystems/nomnom
Make the election instructions and disclaimers a property of the election, not a template
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 15
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
The election instructions should be admin-editable, per-election.
- markdown support is required
- possibly cache the HTML rendering? Probably doesn't matter at this scale.
- admin editable
- feedback email should be a function of the election
Partly driven by the idea of an election that isn't a Hugos (thanks, Jesi...)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the election model, admin editing interface, instruction template, and feedback-email code. Trace how election-specific data is stored and rendered, then identify the existing tests covering these paths. Done means instructions and the feedback email are configurable per election, with Markdown rendering and non-Hugo elections supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100