Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tracker: theming and branding — dark mode, logos, Swagger

Open
  • Is something wrong?
#293 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

This is an umbrella tracker, not a standalone change: start with sub-issues #240, #253, #247, #262, and #174, which define the individual work. Read each sub-issue and its referenced files before choosing a task; completion means landing that work under its own issue, since this tracker closes none of them directly.

Written by the indexing model from the issue text.

Description

enhancement tracker

Summary

Five theming issues, two pairs of which edit the same render sites.

Why these are grouped

#247 and #262 touch the same places. #247 adds dark-mode and light-mode ISU logo variants (the current single logo forces a white box around itself to stay legible on dark backgrounds); #262 standardizes the logo's size across pages. Both edit every site where the logo renders, and #262's own body already notes the interaction. #40 (hyperlink the CS logo at the bottom of the home page) is a third edit to one of those same sites.

#240 and #253 are both dark-mode correctness. #240 is the light-mode flash on navigation (ThemeModeContext renders light on the server and on first paint, applying the saved preference only in a post-mount effect) plus respecting the OS theme on first load. #253 is a hardcoded bgcolor: 'grey.100' in PopoverTooltipClick.js making the tooltip header unreadable in dark mode. Both are "a theme value was fixed where it should have been dynamic".

#174 (Swagger's colors make the text hard to read) is the same class of problem on the API docs surface.

Suggested order

  1. #240 — fix theme resolution at the root, first
  2. #253 — the hardcoded tooltip color it exposes
  3. #247 + #262 + #40 — one pass over every logo render site
  4. #174 — Swagger theme

Sub-issues

Tracked as sub-issues below. None of them are closed by this issue — each closes as its own work lands.

Related (not re-parented)

Opened by other contributors, so linked for context only — their state is unchanged:

  • #40 — CS logo at bottom of home page needs to be hyperlinked (like "About Us" page) (@norkish)

Issue Handling

Umbrella/tracker issue grouping existing work; no new scope is introduced here. Nothing is closed by this issue directly.

Dominant language
JavaScript
Stars
3
Forks
18
Avg merge
1d 3h
Merged PRs (30d)
35

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 ReduxISU/Redux_GUI

All issues in ReduxISU/Redux_GUI

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.