Skip to content
Ayush RoyEditorial portfolio system
HomeAboutProjectsExperienceSkillsGamesContact
Resume
Continue to next

Guided journey

Continue the intentional walkthrough instead of jumping randomly.

Next: About
Founder of Yor Zenith - Full Stack Developer Intern CandidateAyush Roy

Portfolio, profile, case studies, games, achievements, and dashboard surfaces now share one editorial system rooted in the hobbies design language.

Explore
AboutProjectsExperienceSkillsContact
GamesAchievementsStatsTimelineDashboardProfileSearchOnboarding
Resources
ResumeCVBlogDevLogGalleryMediaSteamHobbiesFunValue EducationAvatar3D DemoSettingsGitHub
ayushroy.dev@gmail.com+91 8918940799linkedin.com/in/yorayriniwnl
Copyright 2026 / Built with Next.js

Studio Notes / Portfolio System

Turning Portfolio Claims into Verified Signals

Refreshing the portfolio meant replacing stretched claims with resume-backed skills, live GitHub repositories, and project descriptions that match the evidence.

← All Notes
Case Study2026-04-13·6 min read
portfolioresumecase-studydesign-system

The Problem With Inflated Portfolios

Most portfolio sites make the same mistake: they describe skills with superlatives that the projects cannot back up. "Expert in React" with one to-do app. "Machine learning engineer" with a single Kaggle notebook. The gap between the words and the evidence is obvious to anyone hiring.

This portfolio started in the same place. The first draft used confident language that wasn't matched by verifiable work. The fix wasn't cosmetic — it required changing how every claim was sourced.

What "Verified Signal" Actually Means

A verified signal is a claim that can be cross-referenced. It points to a specific GitHub repository, a live deployment, a concrete tool used in a real project, or a role listed on a resume with dates.

The opposite is a placeholder claim: general language that sounds impressive but floats free of any evidence. "Strong communication skills." "Passionate about building scalable systems." These aren't lies, but they're not signals either.

The Refactor Process

The process had three phases:

Phase 1 — Audit. Every skill listed was checked against the actual projects. Skills without project backing were moved to a separate section or removed.

Phase 2 — Match language to evidence. Project descriptions were rewritten to describe what was actually built, not what could theoretically be built. If a feature wasn't shipped, it was marked as planned or removed.

Phase 3 — Surface the repositories. Live GitHub links were added for every project where the code is public. Projects without public repos are labelled accurately.

The Design System Connection

Fixing the content also meant fixing the presentation. A portfolio that presents accurate claims needs a layout that respects the reader's time — no flashy animations that obscure thin content, no walls of text that bury the signal.

The blog route became the anchor for this design decision. Its spacing, typography, and card structure now inform the entire app. When every page inherits from the same system, the honesty of the content and the clarity of the layout reinforce each other.

What Stays Placeholder

Some sections are still explicitly labelled as placeholder work. The goal isn't to pretend everything is finished — it's to be clear about what is real and what is still in progress. That transparency is itself a signal about how the work is approached.