Remove unused JS (modal.js, theme-switcher*.js) and fix CSS typos

Open Beginner friendly
  • Is something wrong?
#189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
css, javascript, jekyll
Domain
frontend

Research direction

Start in assets/js/ and _layouts/base.html, where the issue says modal.js and the unused theme-switcher files are loaded or sit. Remove the modal.js <script> tag and the unused files, then fix the justify-content: top declaration and rename .feautured-topic-links in custom.css and _pages/index.md line 209. Done when a grep finds no remaining references and the Jekyll site still builds.

Written by the indexing model from the issue text.

Description

good first issue

Summary

Small cleanups in assets/:

  • assets/js/modal.js loads on every page, but nothing uses it. No template has data-target or calls toggleModal. Removing it and its <script> tag from _layouts/base.html saves a request and also resolves #95.
  • assets/js/theme-switcher.js and assets/js/theme-switcher copy.js aren't used. Only minimal-theme-switcher.js is loaded, and the copy has a space in its filename.
  • Invalid CSS: .card, .card-row { justify-content: top; } in custom.css. top isn't a valid value, so browsers drop the declaration. It's either meant to be flex-start or can be deleted.
  • Typo: the class .feautured-topic-links (custom.css and _pages/index.md:209) should be featured. Rename it in both places.

Evidence (2026-10-14)

grep across _layouts, _includes and _pages found no uses of data-target or toggleModal. base.html only loads minimal-theme-switcher.js, modal.js and navigation.js.

Generated by Claude Code

Dominant language
HTML
Stars
1
Forks
6
Avg merge
1d 52m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CivicTechTO/civictech.ca

All issues in CivicTechTO/civictech.ca

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.