Volunteering at Civic Tech Toronto on Civic Dashboard
What Civic Tech Toronto is, how Civic Dashboard helps residents follow City Council, and the five fixes I have written for it, from search that matched everything to a security upgrade that would have taken the site down.
· 5 min read · Civic tech, Volunteering, Next.js
Civic Tech Toronto
Civic Tech Toronto began on 6 June 2015, when a group of residents spent a day working on civic and social problems in their own neighbourhoods. Since that summer it has met every Tuesday evening, now in person and online, and it has passed its 500th hacknight. It is run entirely by volunteers.
A hacknight opens with introductions and a featured talk, and then people split up to work on the community projects. Those projects are open to new contributors, which is how I joined one in September 2026 as a volunteer developer.
Civic Dashboard
The project I work on is Civic Dashboard, at civicdashboard.ca. It makes Toronto City Council easier to follow. Residents can see which items are coming up, read their councillor's voting record, get an email when an item they care about is on an agenda, and send a comment or ask to speak in one step.
It works from the City of Toronto's public agendas and voting records. Council publishes each agenda a week before the meeting, so an email alert gives people time to act before an item is decided. That makes the quiet bugs matter: if search or alerts are slightly wrong, someone misses their window and never knows why.
What I've fixed
Three of my pull requests are merged and two are in review.
Searches in brackets matched everything
A search for (housing) returned every item, (transit or bike) only searched for transit, and -(towing) showed only towing items instead of hiding them. Email alerts use the same parser, so anyone subscribed to (housing) got an email for every new item.
The parser counted the closing bracket's position from after the opening bracket and then used it as if it counted from the start. Converting it to the right position in the two bracket cases fixed it, and searches without brackets behave exactly as before. A workflow rebuilds every saved subscription on merge, so existing subscribers were fixed automatically.
The feedback form could ping a whole Slack channel
The feedback form posted what visitors typed straight into the team's Slack channel. Slack reads <!channel> and <url|label> as a mention or a link, so anyone could ping the whole channel or post a disguised link. Every field is now escaped first, so Slack shows it as plain text. I tested it against a test Slack webhook with both kinds of feedback form.
Pages that repeated or skipped items
One issue, four bugs. Infinite scroll could show an item twice or skip one, because items from the same meeting share a date and the sort had no tiebreaker. A councillor's voting record could change between page loads. A failed unsubscribe still hid the subscription. And the public APIs accepted any page size. Each fix is one to three lines.
Agenda pages that would crash in the new term (in review)
An upcoming item whose committee wasn't in the database returned a server error, because the page read the committee's name while rendering. Committee IDs change every council term, so this would hit every item of the new term. The page now loads, and only the comment and speak actions are hidden when there is no committee to send them to.
A security upgrade that would have taken the site down (in review)
A high-severity denial-of-service advisory affected the site's version of Next.js. Upgrading Next.js on its own made every page return an error on Cloudflare, because the deploy adapter didn't support the new release yet. The pull request upgrades Next.js together with the lowest adapter and Wrangler versions that support it. Production audit findings went from 8, one of them critical, to 4 with none critical.
The full write-ups, with screenshots of Civic Dashboard and the council it follows, are on the Civic Tech Toronto page of this site.