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

chore(assets): Convert org-explorer-logo.png to SVG

Open Beginner friendly
#301 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #303 by @shashank-tomar0 — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start by locating public/org-explorer-logo.png and every reference to it — the issue names HomePage, Navbar, README and the social meta tags (og:image) — then add the optimized SVG at src/assets/og-logo.svg. Check the closed, unmerged PR #303 first to see why that attempt was abandoned before redoing it. Done means the PNG is deleted, all references point at the SVG, and npm run build (vite build) passes. Note some acceptance-criteria text is truncated in the issue body, so confirm wording with a maintainer.

Written by the indexing model from the issue text.

Description

enhancement

Description

Convert the main logo from PNG to SVG format for better scalability and performance.

Context

From :

  • Convert public/org-explorer-logo.png to svg. (open to any contributor)
  • Redesign OrgExplorer svg: src/assets/og-logo.svg. (open to any contributor)

Acceptance Criteria

  • converted to
  • SVG optimized (SVGO or similar)
  • All references updated in codebase (HomePage, Navbar, README if applicable)
  • PNG file removed from repo
  • Build passes (

[email protected] build
vite build)

  • Visual regression check: logo renders correctly at all sizes

Optional Bonus

  • Refresh for social sharing cards (og:image)

Notes

  • Current PNG: 435 KB → SVG should be ~5-15 KB
  • Logo used in: HomePage hero, Navbar, README.md, social meta tags
  • No functional changes — asset swap only
Dominant language
JavaScript
Stars
42
Forks
124
Avg merge
2d 22h
Merged PRs (30d)
10

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 AOSSIE-Org/OrgExplorer

All issues in AOSSIE-Org/OrgExplorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.