Verto.sh
Rebrand & UX for an Open-Source collaboration platform
TL;DR
Problem: FirstIssue.dev had a dated look and very basic UX; Every extra click lost new contributors.
My move: Re-named, re-branded, and rebuilt the interface - then layered in filters, tags, and clearer hierarchy.
Impact: Traffic almost doubled, the project hit Hacker News front page, and a broader mix of senior devs now promote the platform.
Link: https://www.verto.sh/
Timebound: 3 months
Role: UX/UI Designer
Tools: Figma, Miro, Online interviews, google forms
Context & unknowns
A new owner took over the the unused and outdated site and asked for “modern, playful, reliable.”
I walked in not knowing:
Who really used it? Was it just first-timers or any seasoned folks?
What caused users to leave? Old visuals, no filters, or both?
Can we update the look quickly, then improve the UX later without rebuilding everything?
The initial design status
Gray areas
78 % of clicks were on the left half of the page (NN/g study)
Users asked for “language” & “difficulty” filters
From grey areas to clear moves
What I did with it
Two-column, central grid: filters left, repo list right
Tag + multi-select filter bar
Brand felt “too student” for senior devs.
Xtra challenge: the owner decided to do a bold move and change the platform name
Re-name to Verto.sh (by owner) + retro-arcade typography (Endless Boss Battle)
Bumps along the way
Long repo names wrapped to three lines; added truncation + full-name tooltip
Initial filter colors had poor contrast on the green brand; changed to magenta and tested again.
Some visuals of the work done
Leading the work
Started quickly by studying issue-tracker sites (CodeTriage, Up-For-Grabs, CodeSee) to find UI patterns that help newcomers make their first PR.
Kept the plan clear with a Trello board labeled “Today / Next / Someday” and held two 30-minute check-ins weekly with the solo developer to keep design and code aligned.
Tested prototypes live by sharing Figma links in GitHub Discussions, collecting feedback from a dozen open-source contributors to make final improvements before launch.
Impact
What shipped & why it mattered
Complete brand refresh - new name (Verto.sh), neon-retro logo, and bright magenta-blue colors. Why it mattered: created a clear identity that appeals to both new and experienced developers and shaped the tone for all social media.
Two-column repo layout - repos listed on the right, filter shown on the left, no back-and-forth; new users find a suitable issue in about 30 seconds to 1 minute.
Filters for language, label, and difficulty - beginners focus on simple stuff, experts find harder tasks; 68% said it made issue finding easier.
Marketing features added - newsletter signup in footer and GitHub star button in header: gained 400+ new subscribers and a 25% rise in repo stars within two weeks.
Hacker-News - front-page spot doubled traffic temporarily and increased returning users long-term.
Reflection
The bright new neon logo caught attention, but the real success was making things clear, for users and code reviewers dealing with many wrongly tagged issues.
The main lesson: launch with just enough polish, then add UX details once real users come.
If I did it again, I'd test filters with real GitHub data from the start; fake data missed issues we fixed later.
Still, watching both new and experienced developers use filters and open PRs quickly showed the redesign worked well.